Question

A model-driven telemetry collector receives interface counter data from 40 IOS-XE routers using a dial-out gRPC subscription with a 1-second cadence. Operators notice periodic gaps in the time-series data, and device logs show 'telemetry: unable to send segment, dropping data' messages during peak traffic periods. CPU on the routers spikes near the collection intervals. The collector itself shows no ingestion errors and is far below its resource limits. What is the MOST likely cause and appropriate fix?

Accepted Answer

The 1-second cadence overwhelms the device export pipeline; increase the sample interval to a more sustainable value to reduce per-device export load

Answer

The collector's TLS certificate has expired; renew and redeploy the CA-signed certificate to restore the stream

Answer

The subscription is configured as dial-in instead of dial-out; switch to a periodic dial-in subscription to buffer data

Answer

The encoding is set to self-describing GPB; switch to JSON encoding to reduce the payload size the device must generate