Agent skill · software engineering · nvidia
doca-telemetry-exporter
Use this skill when the user is doing hands-on DOCA Telemetry Exporter programming on a host where DOCA is installed — defining a doca_telemetry_exporter_schema and event types, creating sources, picking a publish surface (typed events / opaque events / the metrics counter-gauge-histogram API / OTLP logs / NetFlow), walking the schema-then-source lifecycle, or debugging DOCA_ERROR_* failures from the exporter API. Trigger even when the user does not explicitly mention "DOCA Telemetry Exporter" or "doca_telemetry_exporter_*" — typical implicit phrasings include "publishing counters from my DOCA app", "BAD_STATE when I report an event", "consumer/DTS sees nothing but my report succeeded", "how do I export NetFlow/IPFIX records", or "should I link the exporter or the telemetry service". Refuse and route elsewhere for the receiving DOCA Telemetry Service (DTS), plain stdout logging via doca_log, or real-time event subscription back into the app via doca-comch — those belong to other skills.
Why this skill is useful
Provides specific commands and workflows for configuring and debugging the DOCA Telemetry Exporter that are not widely known.
What it needs
Requires doca installed locally. About 9k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
DOCA Telemetry Exporter Examples "Publishing counters from my DOCA app." — this is in scope. Walk schema-then-source; do not configure DTS here. "BADSTATE when I report an event." — check the lifecycle order before changing the report call. Instructions Follow Loading order below. Open the tasks companion for configure / publish / debug. Open the capabilities companion for publish surfaces. Do not open every companion file. Where to start: This skill assumes DOCA is already installed and the user is doing hands-on telemetry-exporter work — emitting structured application telemetry (counters / events) from a DOCA-using program to an external consumer. Open the tasks companion if the user wants to do something (configure / build / modify + rebuild / run / test / debug); open the capabilities companion when the question is what can the exporter express on this install. If the user has not installed DOCA yet, route to doca-setup/SKILL.md first. If the user is confused about whether they want this library or the DOCA Telemetry Service (the receiver) — read the exporter-vs-service rule in the capabilities companion before configuring anything. This library is NOT a DOCA Core context. There is no docactxstart() for the exporter and no per-docadevinfo capability-query family (its docacaps dump is a stub). The lifecycle is schemainit → configure exporters → register type(s) → schemastart → sourcecreate → sourcestart → report → flush → destroy. Example questions this skill answers well The CLASSES of telemetry-exporter questions this skill is built to answer, each with one worked example. The agent should treat the class as the load-bearing piece — the worked example is a single instance. "Which library do I want — the exporter or the telemetry service?" — worked example: "I want my DOCA Flow program to publish a per-second packets-processed counter to a downstream collector — which DOCA artifact do I link?". …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/doca-telemetry-exporter