Nginx and Cortex 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 Nginx plugin for Telegraf is designed to collect status metrics from Nginx web servers, providing real-time insights into server operation metrics.
This plugin enables Telegraf to send metrics to Cortex using the Prometheus remote write protocol, allowing seamless ingestion into Cortex’s scalable, multi-tenant time series storage.
Integration details
Nginx
This plugin gathers status metrics from Nginx. It utilizes the ngx_http_stub_status_module to collect basic metrics related to the server’s performance. The plugin provides valuable insights into active connections, requests handled, and the current state of various metrics. This real-time data is essential for monitoring web server performance and ensuring optimal operations. The configuration allows users to specify the URL for the Nginx status endpoint, set timeouts, and configure TLS settings if necessary.
Cortex
With Telegraf’s HTTP output plugin and the prometheusremotewrite
data format you can send metrics directly to Cortex, a horizontally scalable, long-term storage backend for Prometheus. Cortex supports multi-tenancy and accepts remote write requests using the Prometheus protobuf format. By using Telegraf as the collection agent and Remote Write as the transport mechanism, organizations can extend observability into sources not natively supported by Prometheus—such as Windows hosts, SNMP-enabled devices, or custom application metrics—while leveraging Cortex’s high-availability and long-retention capabilities.
Configuration
Nginx
[[inputs.nginx]]
## An array of Nginx stub_status URI to gather stats.
urls = ["http://localhost/server_status"]
## Optional TLS Config
# tls_ca = "/etc/telegraf/ca.pem"
# tls_cert = "/etc/telegraf/cert.pem"
# tls_key = "/etc/telegraf/key.pem"
## Use TLS but skip chain & host verification
# insecure_skip_verify = false
## HTTP response timeout (default: 5s)
response_timeout = "5s"
Cortex
[[outputs.http]]
## Cortex Remote Write endpoint
url = "http://cortex.example.com/api/v1/push"
## Use POST to send data
method = "POST"
## Send metrics using Prometheus remote write format
data_format = "prometheusremotewrite"
## Optional HTTP headers for authentication
# [outputs.http.headers]
# X-Scope-OrgID = "your-tenant-id"
# Authorization = "Bearer YOUR_API_TOKEN"
## Optional TLS configuration
# tls_ca = "/path/to/ca.pem"
# tls_cert = "/path/to/cert.pem"
# tls_key = "/path/to/key.pem"
# insecure_skip_verify = false
## Request timeout
timeout = "10s"
Input and output integration examples
Nginx
-
Web Performance Monitoring: Use the Nginx plugin to gather performance metrics from various Nginx servers across your infrastructure. By visualizing these metrics in real-time dashboards, teams can track performance trends, identify bottlenecks, and enhance the user experience on their web applications. Implementing such monitoring allows businesses to proactively address performance issues before they impact end-users.
-
Load Balancer Monitoring: Integrate this plugin with your load balancers to track the performance of backend Nginx servers. By collecting statistics like ‘active connections’ and ‘requests handled’, your operations team can ensure that traffic is flowing optimally and that no single server is overwhelmed. This proactive approach to load balancing prevents service downtime and enhances user experience.
-
Automated Alerting Systems: Combine the Nginx plugin with alerting services to automatically notify your team when a server’s metrics exceed predefined thresholds. For instance, if the number of active connections is too high, the system can trigger alerts so that corrective actions can be taken immediately, thus maintaining service quality and reliability.
-
Historical Data Analysis: Store the metrics collected by the Nginx plugin in a time-series database to analyze historical performance trends. This analysis can uncover periods of high traffic or poor performance, allowing for data-driven decisions about infrastructure scaling and optimization. By understanding past trends, organizations can better prepare for future demands.
Cortex
-
Unified Multi-Tenant Monitoring: Use Telegraf to collect metrics from different teams or environments and push them to Cortex with separate
X-Scope-OrgID
headers. This enables isolated data ingestion and querying per tenant, ideal for managed services and platform teams. -
Extending Prometheus Coverage to Edge Devices: Deploy Telegraf on edge or IoT devices to collect system metrics and send them to a centralized Cortex cluster. This approach ensures consistent observability even for environments without local Prometheus scrapers.
-
Global Service Observability with Federated Tenants: Aggregate metrics from global infrastructure by configuring Telegraf agents to push data into regional Cortex clusters, each tagged with tenant identifiers. Cortex handles deduplication and centralized access across regions.
-
Custom App Telemetry Pipeline: Collect app-specific telemetry via Telegraf’s
exec
orhttp
input plugins and forward it to Cortex. This allows DevOps teams to monitor app-specific KPIs in a scalable, query-efficient format while keeping metrics logically grouped by tenant or service.
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