splunk-observability-nvidia-gpu-integration

Render NVIDIA DCGM Exporter telemetry into Splunk Observability Cloud with a Prometheus receiver.

36|7|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/chambear2809/splunk-cisco-skills --skill splunk-observability-nvidia-gpu-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: splunk-observability-nvidia-gpu-integration
Source: https://github.com/chambear2809/splunk-cisco-skills/tree/main/skills/splunk-observability-nvidia-gpu-integration
Command: npx skills add https://github.com/chambear2809/splunk-cisco-skills --skill splunk-observability-nvidia-gpu-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Render NVIDIA GPU telemetry from DCGM Exporter into Splunk Observability Cloud. It avoids Autodetect collisions with the Splunk OTel chart and provides end-to-end GPU observability, including dashboards, detectors, and preflight handoffs.

Core Features & Use Cases

  • Dual-label pod discovery for DCGM Exporter across GPU Operator and standalone deployments.
  • Standalone, reusable skill that renders a dedicated receiver and metrics pipeline named receiver_creator/dcgm-cisco and metrics/nvidia-metrics.
  • Optionally patches DCGM pod labels to expose per-workload labels; generates dashboards, detectors, handoffs, and metadata.

Quick Start

Render the overlay and validate it against your cluster using the provided setup.sh workflow.

Frequently Asked Questions about splunk-observability-nvidia-gpu-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect NVIDIA GPU metrics from DCGM Exporter in Splunk Observability Cloud?

You can collect NVIDIA GPU metrics in Splunk Observability Cloud by rendering a custom Prometheus receiver and metrics pipeline that ingests DCGM Exporter telemetry across Kubernetes clusters, supporting both GPU Operator and standalone deployments.

What is the best way to avoid Splunk OTel chart autodetect collisions when adding NVIDIA GPU telemetry?

To avoid Splunk OTel chart autodetect collisions when adding NVIDIA GPU telemetry, use a uniquely named receiver_creator (dcgm-cisco by default) and a dedicated metrics pipeline to prevent chart integration conflicts.

Can I track per-workload GPU metrics using DCGM pod labels in Splunk Observability?

Yes, you can track per-workload GPU metrics in Splunk Observability by optionally patching DCGM pod labels to expose workload-level metadata, enabling detailed telemetry correlation for Kubernetes deployments.

Does this NVIDIA GPU integration support both GPU Operator and legacy DCGM deployments?

Yes, the NVIDIA GPU integration supports both GPU Operator deployments and legacy DCGM exporters by using dual-label pod discovery to find and ingest telemetry across different Kubernetes cluster configurations.

What prebuilt dashboards and detectors are available for NVIDIA GPU telemetry in Splunk Observability?

Prebuilt dashboards and detectors for NVIDIA GPU telemetry in Splunk Observability are generated alongside the rendered overlay, providing immediate visibility into GPU health and performance metrics without manual configuration.

How do I validate a DCGM Exporter receiver overlay against my Kubernetes cluster?

You can validate a DCGM Exporter receiver overlay against your Kubernetes cluster using the provided setup workflow script, which outputs a ready-to-apply overlay and patch artifacts for your Splunk Observability deployment.