Kernel and Databricks Integration
Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.
5B+
Telegraf downloads
#1
Time series database
Source: DB Engines
1B+
Downloads of InfluxDB
2,800+
Contributors
Table of Contents
Powerful Performance, Limitless Scale
Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.
See Ways to Get Started
Input and output integration overview
The Kernel plugin collects various statistics about the Linux kernel, including context switches, page usage, and entropy availability.
Use Telegraf’s HTTP output plugin to push metrics straight into a Databricks Lakehouse by calling the SQL Statement Execution API with a JSON-wrapped INSERT or volume PUT command.
Integration details
Kernel
The Kernel plugin is designed exclusively for Linux systems and gathers essential kernel statistics that are not covered by other plugins. It primarily focuses on the metrics available in /proc/stat
, as well as the entropy available from /proc/sys/kernel/random/entropy_avail
. Additional functionalities include the capture of Kernel Samepage Merging (KSM) data and Pressure Stall Information (PSI), requiring Linux kernel version 4.20 or later. This plugin provides a comprehensive look into system behaviors, enabling better understanding and optimization of resource management and usage. The metrics it collects are critical for monitoring system health and performance.
Databricks
This configuration turns Telegraf into a lightweight ingestion agent for the Databricks Lakehouse. It leverages the Databricks SQL Statement Execution API 2.0, which accepts authenticated POST requests containing a JSON payload with a statement
field. Each Telegraf flush dynamically renders a SQL INSERT (or, for file-based workflows, a PUT ... INTO /Volumes/...
command) that lands the metrics into a Unity Catalog table or volume governed by Lakehouse security. Under the hood Databricks stores successful inserts as Delta Lake transactions, enabling ACID guarantees, time-travel, and scalable analytics. Operators can point the warehouse_id
at any serverless or classic SQL warehouse, and all authentication is handled with a PAT or service-principal token—no agents or JDBC drivers required. Because Telegraf’s HTTP output supports custom headers, batching, TLS, and proxy settings, the same pattern scales from edge IoT gateways to container sidecars, consolidating infrastructure telemetry, application logs, or business KPIs directly into the Lakehouse for BI, ML, and Lakehouse Monitoring. Unity Catalog volumes provide a governed staging layer when file uploads and COPY INTO
are preferred, and the approach aligns with Databricks’ recommended ingestion practices for partners and ISVs.
Configuration
Kernel
[[inputs.kernel]]
## Additional gather options
## Possible options include:
## * ksm - kernel same-page merging
## * psi - pressure stall information
# collect = []
Databricks
[[outputs.http]]
## Databricks SQL Statement Execution API endpoint
url = "https://{{ env "DATABRICKS_HOST" }}/api/2.0/sql/statements"
## Use POST to submit each Telegraf batch as a SQL request
method = "POST"
## Personal-access token (PAT) for workspace or service principal
headers = { Authorization = "Bearer {{ env "DATABRICKS_TOKEN" }}" }
## Send JSON that wraps the metrics batch in a SQL INSERT (or PUT into a Volume)
content_type = "application/json"
## Serialize metrics as JSON so they can be embedded in the SQL statement
data_format = "json"
json_timestamp_units = "1ms"
## Build the request body. Telegraf replaces the template variables at runtime.
## Example inserts a row per metric into a Unity-Catalog table.
body_template = """
{
\"statement\": \"INSERT INTO ${TARGET_TABLE} VALUES {{range .Metrics}}(from_unixtime({{.timestamp}}/1000), {{.fields.usage}}, '{{.tags.host}}'){{end}}\",
\"warehouse_id\": \"${WAREHOUSE_ID}\"
}
"""
## Optional: add batching limits or TLS settings
# batch_size = 500
# timeout = "10s"
Input and output integration examples
Kernel
-
Memory Optimization through KSM: Utilize the KSM capabilities of this plugin to monitor memory usage patterns in your applications and dynamically adjust the memory allocation strategy based on shared page usage metrics. By analyzing the data collected, you can identify opportunities for consolidating memory and optimizing performance without manual intervention.
-
Real-time System Health Monitoring: Integrate the metrics collected by the Kernel plugin into a real-time dashboard that visualizes key kernel statistics including context switches, interrupts, and entropy availability. This setup allows system administrators to proactively respond to performance issues before they escalate into critical failures, ensuring smooth operation of Linux servers.
-
Enhanced Anomaly Detection: Combine the data from this plugin with machine learning models to predict and detect anomalies in kernel behavior. By continuously monitoring metrics like process forking rates and entropy levels, you can implement an adaptive alerting system that triggers on performance anomalies, allowing for quick responses to potential issues.
-
Resource Usage Patterns Analysis: Use the Pressure Stall Information collected by the plugin to analyze resource usage patterns over time and identify potential bottlenecks under load conditions. By adjusting application performance based on the PSI metrics, you can improve overall resource management and maintain service reliability under varying workloads.
Databricks
- Edge-to-Lakehouse Telemetry Pipe: Deploy Telegraf on factory PLCs to sample vibration metrics and post them every second to a serverless SQL warehouse. Delta tables power PowerBI dashboards that alert engineers when thresholds drift.
- Blue-Green CI/CD Rollout Metrics: Attach a Telegraf sidecar to each Kubernetes canary pod; it inserts container stats into a Unity Catalog table tagged by
deployment_id
, letting Databricks SQL compare error-rate percentiles and auto-rollback underperforming versions. - SaaS Usage Metering: Insert per-tenant API-call counters via the HTTP plugin; a nightly Lakehouse query aggregates usage into invoices, eliminating custom metering micro-services.
- Security Forensics Lake: Upload JSON batches of Suricata IDS events to a Unity Catalog volume using
PUT
commands, then runCOPY INTO
for near-real-time enrichment with Delta Live Tables, producing a searchable threat-intel lake that joins network logs with user session data.
Feedback
Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.
Powerful Performance, Limitless Scale
Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.
See Ways to Get Started
Related Integrations
Related Integrations
HTTP and InfluxDB Integration
The HTTP plugin collects metrics from one or more HTTP(S) endpoints. It supports various authentication methods and configuration options for data formats.
View IntegrationKafka and InfluxDB Integration
This plugin reads messages from Kafka and allows the creation of metrics based on those messages. It supports various configurations including different Kafka settings and message processing options.
View IntegrationKinesis and InfluxDB Integration
The Kinesis plugin allows for reading metrics from AWS Kinesis streams. It supports multiple input data formats and offers checkpointing features with DynamoDB for reliable message processing.
View Integration