Decoding Junos Telemetry Interface UDP Data at the Collector

The collector must start a listener on the remote address or port combination to read the incoming data. The incoming data can be decoded using the telemetry_top.proto and the sensor proto files.

To simplify the decoding procedure, the collectors can load all the proto files shipped as part of the Telemetry Software package to decode the incoming data.

You can use UNIX utilities to decode Junos telemetry interface data on a server, or collector see, Decoding Junos Telemetry Interface Data With UNIX Utilities

Note:

1. Verify streaming data on both management and WAN interfaces. Specify the appropriate address in the streaming server profile.
2. Enums and float are streamed as strings for UDP streaming. Enums will be retained as strings as gNMI uses the same format.
3. The handling of float data type is scoped for a future release.

When telemetry data is streamed over UDP, ensure that data is decoded correctly, and unknown fields are not decoded at the collector.

Below are some issues observed while streaming telemetry data over UDP:

1. Incorrect Decoding: Incorrect decoding implies that telemetry data is not correctly streamed over UDP. In the following example, the data highlighted in bold indicates that the data was not decoded correctly. This behaviour is either due to incorrect encoding or wrong proto file packaging.

   Below is the example of the data being decoded correctly:

2. Incomplete data streaming: Streaming of incomplete data must be verified through data validation in the output file.