Nvidia SMI and Thanos 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 Nvidia SMI 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 Nvidia SMI Plugin enables the retrieval of detailed statistics about NVIDIA GPUs attached to the host system, providing essential insights for performance monitoring.

This plugin sends metrics from Telegraf to Thanos using the Prometheus remote write protocol over HTTP, allowing efficient and scalable ingestion into Thanos Receive components.

Integration details

Nvidia SMI

The Nvidia SMI Plugin is designed to gather metrics regarding the performance and status of NVIDIA GPUs on the host machine. By leveraging the capabilities of the nvidia-smi command-line tool, this plugin pulls crucial information such as GPU memory utilization, temperature, fan speed, and various performance metrics. This data is essential for monitoring GPU health and performance in real-time, particularly in environments where GPU performance directly impacts computing tasks, such as machine learning, 3D rendering, and high-performance computing. The plugin provides flexibility by allowing users to specify the path to the nvidia-smi binary and configure polling timeouts, accommodating both Linux and Windows systems where the nvidia-smi tool is commonly located. With its ability to collect detailed statistics on each GPU, this plugin becomes a vital resource for any infrastructure relying on NVIDIA hardware, facilitating proactive management and performance tuning.

Thanos

Telegraf’s HTTP plugin can send metrics directly to Thanos via its Remote Write-compatible Receive component. By setting the data format to prometheusremotewrite, Telegraf can serialize metrics into the same protobuf-based format used by native Prometheus clients. This setup enables high-throughput, low-latency metric ingestion into Thanos, facilitating centralized observability at scale. It is particularly useful in hybrid environments where Telegraf is collecting metrics from systems outside Prometheus’ native reach, such as SNMP devices, Windows hosts, or custom apps, and streams them directly to Thanos for long-term storage and global querying.

Configuration

Nvidia SMI

[[inputs.nvidia_smi]]
  ## Optional: path to nvidia-smi binary, defaults "/usr/bin/nvidia-smi"
  ## We will first try to locate the nvidia-smi binary with the explicitly specified value (or default value),
  ## if it is not found, we will try to locate it on PATH(exec.LookPath), if it is still not found, an error will be returned
  # bin_path = "/usr/bin/nvidia-smi"

  ## Optional: timeout for GPU polling
  # timeout = "5s"

Thanos

[[outputs.http]]
  ## Thanos Receive endpoint for remote write
  url = "http://thanos-receive.example.com/api/v1/receive"

  ## HTTP method
  method = "POST"

  ## Data format set to Prometheus remote write
  data_format = "prometheusremotewrite"

  ## Optional headers (authorization, etc.)
  # [outputs.http.headers]
  #   Authorization = "Bearer YOUR_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

Nvidia SMI

  1. Real-Time GPU Monitoring for ML Training: Continuously monitor the GPU utilization and memory usage during machine learning model training. This enables data scientists to ensure that their GPUs are not being overutilized or underutilized, optimizing resource allocation and reviewing performance bottlenecks in real-time.

  2. Automated Alerts for Overheating GPUs: Implement a system using the Nvidia SMI plugin to track GPU temperatures and set alerts for instances where temperatures exceed safe thresholds. This proactive monitoring can prevent hardware damage and improve system reliability by alerting administrators to potential cooling issues before they result in failure.

  3. Performance Baselines for GPU Resources: Establish baseline performance metrics for your GPU resources. By regularly collecting data and analyzing trends in GPU usage, organizations can identify anomalies and optimize their workloads accordingly, leading to enhanced operational efficiency.

  4. Dockerized GPU Usage Insights: In a containerized environment, use the plugin to monitor GPU performance from within a Docker container. This allows developers to track GPU performance of their applications in production, facilitating troubleshooting and performance optimization within isolated environments.

Thanos

  1. Agentless Cloud Monitoring: Deploy Telegraf agents across cloud VMs to collect system and application metrics, then stream them directly into Thanos using Remote Write. This provides centralized observability without requiring Prometheus nodes at each location.

  2. Scalable Windows Host Monitoring: Use Telegraf on Windows machines to collect OS-level metrics and send them via Remote Write to Thanos Receive. This enables observability across heterogeneous environments with native Prometheus support only on Linux.

  3. Cross-Region Metrics Federation: Telegraf agents in multiple geographic regions can push data to region-local Thanos Receivers using this plugin. From there, Thanos can deduplicate and query metrics globally, reducing latency and network egress costs.

  4. Integrating Third-Party Data into Thanos: Collect metrics from custom telemetry sources such as REST APIs or proprietary logs using Telegraf inputs and forward them to Thanos via Remote Write. This brings non-native data into a Prometheus-compatible, long-term analytics pipeline.

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