HTTP and Apache Druid Integration

Input and output integration overview

<p>The HTTP plugin allows for the collection of metrics from specified HTTP endpoints, handling various data formats and authentication methods.</p>

<p>This plugin allows Telegraf to send JSON-formatted metrics to Apache Druid over HTTP, enabling real-time ingestion for analytical queries on high-volume time-series data.</p>

Integration details

HTTP

<p>The HTTP plugin collects metrics from one or more HTTP(S) endpoints, which should have metrics formatted in one of the supported input data formats. It also supports secrets from secret-stores for various authentication options and includes globally supported configuration settings.</p>

Apache Druid

<p>This configuration uses Telegraf’s HTTP output plugin with <code>json</code> data format to send metrics directly to Apache Druid, a real-time analytics database designed for fast, ad hoc queries on high-ingest time-series data. Druid supports ingestion via HTTP POST to various components like the Tranquility service or native ingestion endpoints. The JSON format is ideal for structuring Telegraf metrics into event-style records for Druid’s columnar and time-partitioned storage engine. Druid excels at powering interactive dashboards and exploratory queries across massive datasets, making it an excellent choice for real-time observability and monitoring analytics when integrated with Telegraf.</p>

Configuration

HTTP

Apache Druid

Input and output integration examples

HTTP

<ol> <li><strong>Collecting Metrics from Localhost:</strong> The plugin can fetch metrics from an HTTP endpoint like <code>http://localhost/metrics</code>, allowing for easy local monitoring.</li> <li><strong>Using Unix Domain Sockets:</strong> You can specify metrics collection from services over Unix domain sockets by using the http+unix scheme, for example, <code>http+unix:///path/to/service.sock:/api/endpoint</code>.</li> </ol>

Apache Druid

<ol> <li> <p><strong>Real-Time Application Monitoring Dashboard</strong>: Use Telegraf to collect metrics from application servers and send them to Druid for immediate analysis and visualization in dashboards. Druid’s low-latency querying allows users to interactively explore system behavior in near real-time.</p> </li> <li> <p><strong>Security Event Aggregation</strong>: Aggregate and forward security-related metrics such as failed logins, port scans, or process anomalies to Druid. Analysts can build dashboards to monitor threat patterns and investigate incidents with millisecond-level granularity.</p> </li> <li> <p><strong>IoT Device Analytics</strong>: Collect telemetry from edge devices via Telegraf and send it to Druid for fast, scalable processing. Druid’s time-partitioned storage and roll-up capabilities are ideal for handling billions of small JSON events from sensors or gateways.</p> </li> <li> <p><strong>Web Traffic Behavior Exploration</strong>: Use Telegraf to capture web server metrics (e.g., requests per second, latency, error rates) and forward them to Druid. This enables teams to drill down into user behavior by region, device, or request type with subsecond query performance.</p> </li> </ol>

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.