Interface description changes must be reported as they happen, while CPU and memory state has to arrive every 30 seconds at the gNMI collector. Which subscription parameters should the automation configure for model-driven telemetry?
Select an answer to reveal the explanation.
Short Explanation
Your XPath picks the data to watch, like choosing which mailbox to check: use ON_CHANGE for config updates and SAMPLE every 30 seconds for CPU and memory state. Then connect your gNMI client to the collector to deliver both streams.
Full Explanation
A gNMI subscription specifies the paths to monitor and the subscription mode. SAMPLE subscriptions use a sample interval; ON_CHANGE subscriptions report changes when supported by the model and platform. The gNMI client connects to the target, and its connection is made to the collector in this scenario—the collector address is not a receiver parameter in the gNMI subscription. Separate the config and state paths so interface description changes can be reported on change while CPU and memory are sampled every 30 seconds. A single 30-second SAMPLE subscription would delay reporting a description change until a sample. A single ON_CHANGE subscription would not provide the required regular state samples. Practical check: verify ON_CHANGE support for the relevant model and platform, then test that updates arrive as expected.