Agent skill · data analytics · nvidia
doca-telemetry-utils
doca_telemetry_utils command line on a host with DOCA: discover the diagnostic-counter schema, translate counter names to binary Data IDs and back, and check per-device counter support before committing a DOCA Telemetry exporter config. Use this skill when telemetry counters vanish between the exporter and the collector: "my exporter ships but the collector sees nothing", "this metric silently drops downstream", "which counters does this BlueField expose", "translate this 0x... back to a counter name", "what do node / pcie_index / depth mean here", or "is this counter supported on this device", even without naming the tool. Route exporter or collector code to doca-telemetry-exporter / doca-telemetry, DTS deployment to doca-dts, and DOCA install or repair to doca-setup.
Why this skill is useful
Provides domain-specific knowledge on DOCA telemetry, including counter schema discovery and Data ID translation that the AI wouldn't reliably generate on its own.
What it needs
Requires doca installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
DOCA Telemetry Utils Examples "Which diagnostic counters does this BlueField actually expose?" — this is in scope. Enumerate then probe; do not start a collector app here. "My exporter names portrxbytes but nothing shows up downstream." — translate name to Data ID and probe per-device support before changing the exporter. Quick triage: the exporter ships, the collector sees nothing 1. docatelemetryutils get-counters: is the counter known to this release? 2. docatelemetryutils <counter>: print its property options. 3. docatelemetryutils <counter> <properties>: resolve the Data ID. 4. docatelemetryutils <device PCI> <counter> <properties>: "not supported" on this device means the exporter drops it silently; do not commit that counter. 5. docatelemetryutils <0x... Data ID>: reverse-resolve an ID captured on the wire. 6. Check host and BlueField release pairing with doca-version. 7. If every step resolves cleanly, hand off to doca-telemetry ## debug. Quote the tool's output verbatim; never construct Data IDs by hand. Instructions Follow Loading order below. Open the tasks companion for install / run / test. Open the capabilities companion for schema discovery and pairing with the telemetry libraries. Do not open every companion file. Where to start: This is a tool skill for invoking docatelemetryutils — the documented host-side CLI that supports a DOCA Telemetry exporter / collector pipeline by discovering the counter schema, translating counter names ↔ Data IDs, and probing per-device counter support. Open the tasks companion and start at install for the host-side prerequisites and ## run for the three documented invocation classes (enumerate / name→ID / ID→name). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/doca-telemetry-utils