doca-telemetry-exporter
doca-telemetry-exporter is an agent skill published by nvidia, listed under review & testing. It lives in the NVIDIA/skills repository, which has 3,735 GitHub stars and is licensed under Apache-2.0; we last read it on 2026-10-23.
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.
Install
skills is a generic installer for any repository of Claude agent skills -- it reads NVIDIA/skills’s own structure rather than assuming one, the same way this page reads the skill’s own SKILL.md rather than assuming a format.
npx skills add NVIDIA/skills
Maintenance
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.
doca-telemetry-exporter compared with similar skills
| Skill | Publisher | What it does | Repo stars | Last update |
|---|---|---|---|---|
| doca-telemetry-exporter (this page) | nvidia | Use this skill when the user is doing hands-on DOCA Telemetry Exporter programming on a host where DOCA is in… | 3,735 | 2026-10-26 |
| deepstream-sop(same repository) | nvidia | Use this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP I… | 3,735 | 2026-10-26 |
| doca-aes-gcm(same repository) | nvidia | Use this skill when the user is doing hands-on DOCA AES-GCM work on a BlueField DPU or ConnectX NIC — configu… | 3,735 | 2026-10-26 |
| doca-argp(same repository) | nvidia | Use this skill for hands-on DOCA Arg Parser CLI work on a shipped sample or new DOCA-using app — adding / rem… | 3,735 | 2026-10-26 |
| doca-bare-metal-deployment(same repository) | nvidia | Running a DOCA-linked binary directly on the hardware, with no container or kubelet: on host x86 with a BlueF… | 3,735 | 2026-10-26 |
| doca-bench-extension(same repository) | nvidia | Use this skill when the operator is authoring, building, loading, or debugging a custom doca-bench plug-in —… | 3,735 | 2026-10-26 |
| doca-caps(same repository) | nvidia | Use this skill when the user wants to invoke the read-only doca_caps CLI to ask what DOCA sees on this host —… | 3,735 | 2026-10-26 |
Skills from the same repository first, then others for this job by repository stars. Figures are from each repository when we last read it.
Common questions about doca-telemetry-exporter
- What does doca-telemetry-exporter do?
- 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.
- How do I install doca-telemetry-exporter?
- Run npx skills add NVIDIA/skills. The skills installer reads the repository’s own structure, so it works for any repository of agent skills.
- Who publishes doca-telemetry-exporter?
- nvidia.
- Is doca-telemetry-exporter maintained, and what licence does it use?
- Its repository has 3,735 GitHub stars and its state in our directory is listed. Its last commit we recorded was on 2026-10-26. The repository declares the Apache-2.0 licence.
More agent skills for review & testing
- browser-testing-with-devtoolsby addyosmani
- code-review-and-qualityby addyosmani
- code-simplificationby addyosmani
- doubt-driven-developmentby addyosmani
- vitestby antfu
- webapp-testingby anthropic