Cisco Bug: CSCvu03418 - Introduce a separate Hardware timestamp field for Protocol stats
Jun 18, 2020
- Cisco ASR 9000 Series Aggregation Services Routers
Known Affected Releases
Symptom: On DNX like platforms, when data is read from statsd cache (for faster streaming), the graph plotted based on timestamp extracted from stats bag, shows spikes at irregular intervals Conditions: Fetching cached Protocol stats using Telemetry streaming. statsd stores the timestamp of the last collector which updated stats to statsd. An interface can have multiple collectors feeding stats for the same ifhandle for the same stats type. So as and when an update comes from collector, we aggregate the stats, and pick the timestamp of the collector which updated the most latest stats to statsd, and that is the timestamp presented to the client as per design.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases