Nvidia SMI and OpenObserve Integration

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 configuration pairs Telegraf’s HTTP output with OpenObserve’s native JSON ingestion API, turning any Telegraf agent into a first-class OpenObserve collector.

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.

OpenObserve

OpenObserve is an open source observability platform written in Rust that stores data cost-effectively on object storage or local disk. It exposes REST endpoints such as /api/{org}/ingest/metrics/_json that accept batched metric documents conforming to a concise JSON schema, making it an attractive drop-in replacement for Loki or Elasticsearch stacks. The Telegraf HTTP output plugin streams metrics to arbitrary HTTP targets; when the "data_format = "json"" serializer is selected, Telegraf batches its metric objects into a payload that matches OpenObserve’s ingestion contract. The plugin supports configurable batch size, custom headers, TLS, and compression, allowing operators to authenticate with Basic or Bearer tokens and to enforce back-pressure without additional collectors. By reusing existing Telegraf agents already collecting system, application, or SNMP data, organizations can funnel rich telemetry into OpenObserve dashboards and SQL-like analytics with minimal overhead, enabling unified observability, long-term retention, and real-time alerting without vendor lock-in.

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"

OpenObserve

[[outputs.http]]
  ## OpenObserve JSON metrics ingestion endpoint
  url = "https://api.openobserve.ai/api/default/ingest/metrics/_json"

  ## Use POST to push batches
  method = "POST"

  ## Basic auth header (base64 encoded "username:password")
  headers = { Authorization = "Basic dXNlcjpwYXNzd29yZA==" }

  ## Timeout for HTTP requests
  timeout = "10s"

  ## Override Content-Type to match OpenObserve expectation
  content_type = "application/json"

  ## Force Telegraf to batch and serialize metrics as JSON
  data_format = "json"

  ## JSON serializer specific options
  json_timestamp_units = "1ms"

  ## Uncomment to restrict batch size
  # batch_size = 5000

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.

OpenObserve

1. Edge Device Health Mirror: Deploy Telegraf on thousands of industrial IoT devices to capture temperature, vibration, and power metrics, then use this output to push JSON batches to OpenObserve. Plant operators gain a real-time overview of machine health and can trigger maintenance based on anomalies without relying on heavyweight collectors.

2. Blue-Green Deployment Canary: Attach a lightweight Telegraf sidecar to each Kubernetes release-candidate pod that scrapes /metrics and forwards container stats to a dedicated “canary” stream in OpenObserve. Continuous comparison of error rates between blue and green versions empowers the CI pipeline to auto-roll back poor performers within seconds.

3. Multi-Tenant SaaS Billing Pipeline: Emit per-customer usage counters via Telegraf and tag them with tenant_id; the HTTP plugin posts them to OpenObserve where SQL reports aggregate usage into invoices, eliminating separate metering services and simplifying compliance audits.

4. Security Threat Scoring: Fuse Suricata events and host resource metrics in Telegraf, deliver them to OpenObserve’s analytics engine, and run stream-processing rules that correlate spikes in suspicious traffic with CPU saturation to produce an actionable threat score and automatically open tickets in a SOAR platform.

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.