What problem does it solve?
Developers building applications on NVIDIA BlueField DPUs or ConnectX NICs need to read hardware counters (PCC, DPA, diagnostics, adaptive retransmit, PHY, PCI) from a doca_dev, but the six per-domain DOCA Telemetry reader libraries each have their own headers, context types, capability queries, and lifecycle rules that are easy to misuse.
Core Features & Use Cases
- Per-domain reader guidance: Covers the six sub-libraries (doca_telemetry_pcc, _dpa, _diag, _adp_retx, _phy, _pci), including capability queries, context creation, start, read, stop, and destroy lifecycles.
- Error taxonomy and debugging: Maps DOCA_ERROR_* returns (NOT_SUPPORTED, AGAIN, BAD_STATE, INVALID_VALUE, NOT_PERMITTED, IO_FAILED) to reader-specific root causes and fixes.
- Reader vs exporter disambiguation: Prevents the common first-app failure of confusing this counter-reader library with the sibling doca-telemetry-exporter publishing library.
- Use Case: A developer asks their agent to "read PCC counters from my BlueField app" and receives step-by-step guidance to cap-query the device, create the doca_telemetry_pcc context, start it, and read counters with correct sample-window retry behavior.
Quick Start
Ask your agent to read PHY or PCC hardware counters from a doca_dev on your BlueField DPU using the DOCA Telemetry reader library.