domains / families / devops / doca-telemetry

doca-telemetry

separate

Use this skill to read DOCA hardware-counter events from a `doca_dev` through the per-domain Telemetry reader libraries: `doca_telemetry_pcc`, `_dpa`, `_diag`, `_adp_retx`, `_phy`, and `_pci`. It covers capability checks, context creation, startup, and per-domain reads or samples. Trigger for implicit requests such as "read PCC counters from my BlueField app", "sample DPA counter exports", or "expose PHY, PCI, or DIAG counters from this doca_dev". This is the counter-reader surface, not a NetFlow, IPFIX, or local-socket collector. Route publishing and export to `doca-telemetry-exporter`; route the deployed DOCA Telemetry Service to `doca-dts`, and collectors and plain stdout logging elsewhere.

When to use

• read PCC counters
• sample DPA counter exports
• expose PHY, PCI, or DIAG counters
• capability checks
• context creation
• per-domain reads
• hardware-counter-reader work

When not to use

• NetFlow collector
• IPFIX collector
• local-socket collector
• publishing and export
• deployed DOCA Telemetry Service
• collectors and plain stdout logging
• consuming exporter events

Skill page

Source