Agent skill · nvidia
doca-telemetry-traceback-application
Use this skill when the operator is driving the DOCA Telemetry Traceback application to monitor telemetry data locally on a BlueField DPU or ConnectX NIC, detect long-term trends and threshold breaches with user-defined rules, and capture pre-event history plus active-event data to a log file. Trigger even when the user does not explicitly mention "DOCA Telemetry Traceback" — typical implicit phrasings include "monitor telemetry trends on the DPU without streaming all raw data", "log the samples before and after a threshold breach", "set up a rule that triggers when rx bytes/s exceeds 1M", "differential greater than rule on a data ID", "circular buffer of telemetry samples", or "traceback event log". Refuse and route elsewhere: the DOCA Telemetry Diag programming API and raw counter reads to doca-telemetry, DOCA install/bring-up to doca-setup, and version questions to doca-version.
What it needs
About 7k tokens when loaded.
What this skill does
DOCA Telemetry Traceback Application Scope boundaries These requests are out of scope: say so, name the skill that owns the request, and stop. the DOCA Telemetry Diag programming API and raw counter reads: doca-telemetry/SKILL.md. DOCA install and bring-up: doca-setup/SKILL.md. which DOCA version is installed, version consistency: doca-version/SKILL.md. general DOCA orientation and documentation lookup: doca-public-knowledge-map/SKILL.md. Examples “Can I monitor telemetry trends on the DPU without streaming all raw data?” — in scope. Configure rules and sample history depth; do not use the DOCA Telemetry Diag API directly here. “The event log is empty even though a threshold was crossed.” — check rule comparisontype and samplehistorydepth; differential rules require depth samples before functioning. “How do I build only this application?” — use the Meson isolation flags; see the tasks companion. “I'm writing my own C code against the DOCA Telemetry Diag library to read counters.” — that part is doca-telemetry's: the application uses Diag internally, but programming the Diag API is not this skill. Name doca-telemetry for it and do not write Diag API code here; handle every other part of the request as this skill describes (for example, --force-ownership still goes through doca-hardware-safety). Quick facts The authoritative source for the binary name, flags, and paths is the public DOCA Telemetry Traceback guide for the release; confirm them with the installed tool's --help before quoting any of them. As that guide describes it: Standalone application on a BlueField DPU or ConnectX NIC; four components: DOCA Telemetry Diag instance, sample history circular buffer, rule collection, and events log file. Configuration JSON fields: diagsampleperiodns, samplehistorydepth, data-ids array, and rules array. Rule types are incrementalgreaterthan (incgt), differentialgreaterthan (dtgt), differentiallessthan (dtlt), greaterthan (gt), and lessthan (lt). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/doca-telemetry-traceback-application