Doca Telemetry Traceback Application
NVIDIAOfficialCreated by NVIDIA
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The DOCA Telemetry Traceback application is a tool for monitoring telemetry data locally on BlueField DPUs or ConnectX NICs. It allows users to define rules for detecting trends and threshold breaches, capturing both pre-event history and active-event data into a log file. This skill provides guidance on configuring the application via JSON, compiling it from source, and executing it on hardware, while maintaining clear boundaries with other DOCA components like the Telemetry Diag API or installation procedures.
What it does
- Configures telemetry monitoring rules and data IDs via JSON.
- Supports compilation of the application from source code.
- Executes the application on BlueField DPU or ConnectX NIC hardware.
- Captures pre-event and active-event telemetry data to log files.
- Provides troubleshooting steps for empty logs or configuration mismatches.
When to use it
- When you need to monitor telemetry trends locally on a DPU without streaming raw data.
- When you need to set up rules to trigger logs based on threshold breaches.
- When you need to compile the Telemetry Traceback application from source.
- When you are diagnosing issues like empty event logs or unsupported data IDs.
Advantages
- Enables local telemetry processing and traceback logging on supported hardware.
- Provides structured guidance for rule definition and application execution.
- Maintains clear separation between application usage and low-level API programming.
- Integrates with standard DOCA development workflows.
Usage examples
- “How do I set up local telemetry monitoring for port_0_rx_bytes on my DPU?”
- The agent provides the necessary JSON configuration structure and rule definitions to monitor the specified data ID and log history around threshold breaches.
- “Why is my differential_greater_than rule not triggering in the event log?”
- The agent explains the requirement for sample history depth and delta logic, guiding you to verify your configuration parameters.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/nvidia/doca-telemetry-traceback-application/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip doca-telemetry-traceback-application.zip -d .agents/skills
Documentation by NVIDIA
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
comparison_typeandsample_history_depth; 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. Namedoca-telemetryfor it and do not write Diag API code here; handle every other part of the request as this skill describes (for example,--force-ownershipstill goes throughdoca-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:
diag_sample_period_ns,sample_history_depth,data-idsarray, andrulesarray. Rule types areincremental_greater_than(inc_gt),differential_greater_than(dt_gt),differential_less_than(dt_lt),greater_than(gt), andless_than(lt).The circular buffer size is automatically doubled based on the requested depth to ensure equal historical and active event data.
Requires sudo/root privileges; mandatory
-dPCIe address and-rrules JSON; optional--event-logand--force-ownership.Unsupported data IDs are reported; adjust inputs accordingly.
The application stops if the actual sample size or period does not match the requested parameters.
--force-ownershipchanges diag domain ownership; route any use of it throughdoca-hardware-safety/SKILL.md.
Instructions
Follow Loading order below. Open the tasks companion for configure / build / run / debug. Open the capabilities companion for what the application monitors and logs. Do not open every companion file.
Where to start: This is a tool skill for invoking the DOCA Telemetry
Traceback application — the local telemetry monitoring and traceback logging
service that processes telemetry data on the device and writes event logs
when user-defined rules trigger. Open the tasks companion and start at
## configure for the JSON configuration and rule definitions, then
## run for compile and execution. Open the capabilities companion when
the question is what data can be monitored, what rules evaluate, and what
the event log contains. If the user has not installed DOCA yet, route to
doca-setup/SKILL.md first. If the user asks about version, route to
doca-version/SKILL.md. If any step changes hardware or firmware state
(e.g., --force-ownership), route to
doca-hardware-safety/SKILL.md.
How to use this skill. Read this file, then search the companion file
for the ## <name> heading the question needs and read that whole section.
Answer completely from it, quoting only its symbols and commands. Do not
browse docs; use the entry points in doca-public-knowledge-map. Give
environment checks as commands for the user's DOCA host. For out-of-scope
requests, name the skill that owns them and stop.
Compile and run commands are documented in the tasks companion; the
authoritative source is the public guide. The application is distributed as
source and must be compiled before execution. The source is located at
/opt/mellanox/doca/applications/telemetry/traceback/.
Example questions this skill answers well
The CLASSES of telemetry-traceback questions this skill is built to answer, each with one worked example. The class is the load-bearing piece; the worked example is one instance.
“How do I set up local telemetry monitoring with traceback logging?” — worked example: “I want to monitor
port_0_rx_byteson the DPU and log history before and after it exceeds 1 MB/s”. Answered by the JSON configuration and rule definitions in the tasks companion.“What rule types are available and when do they activate/deactivate?” — worked example: “I need a rule that triggers each time a counter increases by a threshold, not just when it exceeds a fixed value”. Answered by the rule definitions in the capabilities companion.
“Why is my differential rule not triggering?” — worked example: “I configured
differential_greater_thanbut the event log stays empty”. Answered by the depth requirement and delta logic in the capabilities companion.“How do I compile and run only this application?” — worked example: “I want to build just the Telemetry Traceback app, not all DOCA applications”. Answered by the Meson isolation flags in the tasks companion.
“What does the event log contain when multiple events overlap?” — worked example: “Two rules trigger at the same time; how are begin/end markers written?”. Answered by the event log lifecycle in the capabilities companion.
“How do I know if my device supports the data IDs I configured?” — worked example: “The application reports unsupported IDs; what do I do?”. Answered by the unsupported data ID handling in the tasks companion.
When to load this skill
Load this skill when the user is — or the agent needs to — drive the DOCA Telemetry Traceback application on a real host or BlueField Arm with DOCA installed (or inside the public NGC DOCA container with the right device passthrough). Concretely:
Configuring JSON rules and data IDs for local telemetry monitoring.
Compiling the application from source.
Running the application with a PCIe address and rules file.
Diagnosing an empty event log, unsupported data IDs, or sample size/period mismatch.
Understanding rule activation/deactivation semantics.
Cross-checking event log output against configured rules.
Do not load this skill for general DOCA orientation, the DOCA Telemetry
Diag programming API, raw telemetry collection, DOCA install, or version
questions. For those, route to
doca-public-knowledge-map/SKILL.md,
doca-setup/SKILL.md, or
doca-version/SKILL.md.
What this skill provides
This is a thin loader. Substantive material lives in two companion files:
the capabilities companion — what the application monitors and logs: the four components, configuration schema, rule definitions with activation/deactivation triggers, event log lifecycle, unsupported data ID behavior, version overlay that redirects to
doca-version/SKILL.md, and the safety policy for--force-ownership.the tasks companion — step-by-step workflows for the in-scope task verbs:
configure(JSON config, rule selection),build(Meson compile all or only this app),run(execution syntax, root, PCIe address),debug(empty log, unsupported IDs, sample mismatch), plus aCommand appendixthat honors the bundle'sdoca-structured-tools-contract/SKILL.mdpreamble.
The skill assumes a host or BlueField where DOCA is already installed (or the public NGC DOCA container is running with the right device passthrough) and the operator has root privileges as required by the public guide.
What this skill deliberately does not ship
This skill is agent guidance, not a samples or scripts bundle. To keep the boundary clean, it deliberately does not contain — and pull requests should not add:
Verbatim flag inventories, subcommand names, or output column names. The public DOCA Telemetry Traceback guide and the installed
--helpon the user's version are the joint source of truth; copying them here pins the skill to one release and silently rots when the application evolves. The skill routes the agent at those sources instead.Pre-baked example output. Output is install-, version-, and device-specific. A captured example will mislead an operator on a different platform / state.
Wrappers, parsers, or scripts in any language that consume the application's output. The output format is documented; users who want to script against it should read the live guide and write the parser against their installed version.
A
samples/orreference/subtree. This is a thin loader for a documented DOCA artifact; substantive material lives on the public page and in--help.
Loading order
Read this skill first to confirm the user's question is in scope (the user wants to monitor telemetry data locally and capture traceback event logs, not use the DOCA Telemetry Diag programming API directly).
For what the application monitors, the configuration schema, rule definitions, event log lifecycle, unsupported data ID behavior, version availability, and safety posture, see the capabilities companion.
For the documented invocations and workflows —
configure,build,run,debug, plus theCommand appendix— see the tasks companion.
Related skills
doca-hardware-safety/SKILL.md— the bundle's hardware/firmware state-change gate. The Telemetry Traceback application is read-only for telemetry data, but the--force-ownershipflag changes diag domain ownership; route any use of that flag through this skill before execution.doca-version/SKILL.md— canonical DOCA version-handling rules. The## Version compatibilitysection in the capabilities companion is a concise overlay that redirects here for the body.doca-setup/SKILL.md— env preparation, install verification, and the I have no install yet path with the public NGC DOCA container. This skill assumes its preconditions are satisfied.doca-public-knowledge-map/SKILL.md— routing to the public DOCA Telemetry Traceback guide and the rest of the public DOCA documentation set. The canonical URL is reached viadoca-public-knowledge-map ## DOCA tools(doca-public-knowledge-map/SKILL.md#doca-tools).doca-structured-tools-contract/SKILL.md— the bundle's detect → prefer → fall back → report contract for structured helper tools. The Command appendix in the tasks companion honors this contract.
Files
- ATTRIBUTION.mdAdded by AutoGineer966 B
- BENCHMARK.md10.8 KiB
- CAPABILITIES.md15.9 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md12.4 KiB
- SKILLCARD.yaml2.6 KiB
- TASKS.md19.5 KiB
- evals/evals.json3.6 KiB
- skill-card.md5.0 KiB
- skill.oms.sig5.2 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
The author says: Requires DOCA SDK installed at /opt/mellanox/doca on Linux with a BlueField DPU or ConnectX NIC, plus root privileges to access hardware-level telemetry data. The application is distributed as source code and must be compiled before execution; the source is located at /opt/mellanox/doca/applications/telemetry/traceback/. Validation steps require a live DOCA install.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- NVIDIA
- Publisher
- NVIDIA (Official)
- Source
- NVIDIA/skills · skills/doca-telemetry-traceback-application · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download doca-telemetry-traceback-application.zip