gNMI 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
<p>The gNMI (gRPC Network Management Interface) Input Plugin collects telemetry data from network devices using the gNMI Subscribe method. It supports TLS for secure authentication and data transmission.</p>
<p>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.</p>
Integration details
gNMI
<p>This input plugin is vendor-agnostic and can be used with any platform that supports the gNMI specification. It consumes telemetry data based on the gNMI Subscribe method, allowing for real-time monitoring of network devices.</p>
Cortex
<p>With Telegraf’s HTTP output plugin and the <code>prometheusremotewrite</code> 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.</p>
Configuration
gNMI
Cortex
Input and output integration examples
gNMI
<ol> <li> <p><strong>Monitoring Cisco Devices</strong>: Use the gNMI plugin to collect telemetry data from Cisco IOS XR, NX-OS, or IOS XE devices for performance monitoring.</p> </li> <li> <p><strong>Real-time Network Insights</strong>: With the gNMI plugin, network administrators can gain insights into real-time metrics such as interface statistics and CPU usage.</p> </li> <li> <p><strong>Secure Data Collection</strong>: Configure the gNMI plugin with TLS settings to ensure secure communication while collecting sensitive telemetry data from devices.</p> </li> <li> <p><strong>Flexible Data Handling</strong>: Use the subscription options to customize which telemetry data you want to collect based on specific needs or requirements.</p> </li> <li> <p><strong>Error Handling</strong>: The plugin includes troubleshooting options to handle common issues like missing metric names or TLS handshake failures.</p> </li> </ol>
Cortex
<ol> <li> <p><strong>Unified Multi-Tenant Monitoring</strong>: Use Telegraf to collect metrics from different teams or environments and push them to Cortex with separate <code>X-Scope-OrgID</code> headers. This enables isolated data ingestion and querying per tenant, ideal for managed services and platform teams.</p> </li> <li> <p><strong>Extending Prometheus Coverage to Edge Devices</strong>: 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.</p> </li> <li> <p><strong>Global Service Observability with Federated Tenants</strong>: 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.</p> </li> <li> <p><strong>Custom App Telemetry Pipeline</strong>: Collect app-specific telemetry via Telegraf’s <code>exec</code> or <code>http</code> 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.</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.
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