What problem does it solve?
Operators standing up a DOCA Telemetry exporter/collector pipeline often hit silent metric drops because exporter configs reference counter names instead of the binary Data IDs the exporter actually ships, or because a counter is not supported on the target BlueField device. This Skill guides agents through the doca_telemetry_utils CLI to discover the counter schema, translate names to Data IDs, and validate per-device support before committing an exporter config.
Core Features & Use Cases
- Schema discovery: Enumerate every diagnostic counter the installed DOCA Telemetry surface knows about via
doca_telemetry_utils get-counters.
- Name ↔ Data ID translation: Resolve counter names plus property dimensions (node, pcie_index, depth) to binary Data IDs, and reverse-resolve captured Data IDs back to names and properties.
- Per-device validation: Probe a specific BlueField PCI address to confirm a counter is supported before committing it to an exporter config, preventing silent metric drops.
- Use Case: An operator reports "my exporter ships but the collector sees nothing." The agent walks the layered error taxonomy, re-resolves the counter, probes the device, and identifies the unsupported counter causing the silent drop.
Quick Start
Ask your agent to enumerate the DOCA diagnostic counters on this host and validate that a chosen counter is supported on your BlueField before adding it to the exporter config.
