An animal control HQ collector will consume interface statistics from model-driven telemetry and must choose an encoding the collector stack supports. What should guide GPB versus JSON selection?
Select an answer to reveal the explanation.
Short Explanation
Encoding is the language the Edge and the collector both speak—GPB is compact binary, JSON is readable text. Pick the one your collector actually understands from what the platform offers. Talking both at once into a monolingual ear just drops the message.
Full Explanation
Model-driven telemetry encodings such as compact GPB and JSON/self-describing formats must match both the device subscription capabilities and the collector’s decoders. Efficiency and tooling often favor GPB at scale, while JSON eases human debugging when supported. Unsupported dual encoding wastes resources; syslog or flash FTP polls are not substitutes for choosing a telemetry encoding.