domains / families / devops / doca-telemetry-utils

doca-telemetry-utils

separate

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.

When to use

• discover the diagnostic-counter schema
• translate counter names to binary Data IDs
• translate binary Data IDs to counter names
• check per-device counter support
• diagnose why telemetry counters vanish between exporter and collector
• enumerate counters exposed by a BlueField DPU
• resolve Data ID properties like node, pcie_index, and depth

When not to use

• exporter or collector code
• DTS deployment
• DOCA install or repair
• developer-side collector library
• developer-side publisher library
• DOCA Telemetry Service deployment

Skill page

Source