Hashicorp Vault and Cortex Integration

Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.

info

This is not the recommended configuration for real-time query at scale. For query and compression optimization, high-speed ingest, and high availability, you may want to consider Hashicorp Vault and InfluxDB.

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 Hashicorp Vault plugin for Telegraf allows for the collection of metrics from Hashicorp Vault services, facilitating monitoring and operational insights.

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

Hashicorp Vault

The Hashicorp Vault plugin is designed to collect metrics from Vault agents running within a cluster. It enables Telegraf, an agent for collecting and reporting metrics, to interface with the Vault services, typically listening on a local address such as http://127.0.0.1:8200. This plugin requires a valid token for authorization, ensuring secure access to the Vault API. Users must configure either a token directly or provide a path to a token file, enhancing flexibility in authentication methods. Proper configuration of the timeout and optional TLS settings further relates to the security and responsiveness of the metrics collection process. As Vault is a critical tool in managing secrets and protecting sensitive data, monitoring its performance and health through this plugin is essential for maintaining operational security and efficiency.

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

Hashicorp Vault

[[inputs.vault]]
  ## URL for the Vault agent
  # url = "http://127.0.0.1:8200"

  ## Use Vault token for authorization.
  ## Vault token configuration is mandatory.
  ## If both are empty or both are set, an error is thrown.
  # token_file = "/path/to/auth/token"
  ## OR
  token = "s.CDDrgg5zPv5ssI0Z2P4qxJj2"

  ## Set response_timeout (default 5 seconds)
  # response_timeout = "5s"

  ## Optional TLS Config
  # tls_ca = /path/to/cafile
  # tls_cert = /path/to/certfile
  # tls_key = /path/to/keyfile

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

Hashicorp Vault

  1. Centralized Secret Management Monitoring: Utilize the Vault plugin to monitor multiple Vault instances across a distributed system, allowing for a unified view of secret access patterns and system health. This setup can help DevOps teams quickly identify any anomalies in secret access, providing essential insights into security postures across different environments.

  2. Audit Logging Integration: Configure this plugin to feed monitoring metrics into an audit logging system, enabling organizations to have a comprehensive view of their Vault interactions. By correlating audit logs with metrics, teams can investigate issues, optimize performance, and ensure compliance with security policies more effectively.

  3. Performance Benchmarking During Deployments: During application deployments that interact with Vault, use the plugin to monitor the effects of those deployments on Vault performance. This allows engineering teams to understand how changes impact secret management workflows and to proactively address performance bottlenecks, ensuring smooth deployment processes.

  4. Alerting for Threshold Exceedance: Integrate this plugin with alerting mechanisms to notify administrators when metrics exceed predefined thresholds. This proactive monitoring can help teams respond swiftly to potential issues, maintaining system reliability and uptime by allowing them to take action before any serious incidents arise.

Cortex

  1. 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.

  2. 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.

  3. 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.

  4. Custom App Telemetry Pipeline: Collect app-specific telemetry via Telegraf’s exec or http 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

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 Integration

Kafka 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 Integration

Kinesis 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