Streaming Telemetry Data Over UDP

date_range 06-Dec-24

arrow_backward

arrow_forward

Streaming Telemetry Data over UDP is based on the dial-out mechanism. The sensor paths are configured through the CLI, and the device sends the data for the configured sensor paths over UDP to the collector's destination address. The destination address is configured through the CLI. While streaming telemetry over UDP from native sensors, the data is sent to the collector over UDP in the protobuf format. For protobuf format information see, Native Protocol Buffers (protobuf) Message Structure

The CLI configuration procedure to stream telemetry data over UDP includes configuring a sensor profile (where resource parameters are specified), a streaming server profile (where remote address and remote-port parameters are specified), and an export profile (where transport protocol, reporting rate, format, and payload-size parameters are specified).

Follow the steps below to configure streaming telemetry data over UDP:

Configure a Streaming Server Profile, see Configuring a Streaming Server Profile.
Configure an Export Profile, see Configuring an Export Profile.
Configure a Sensor Profile, see Configuring a Sensor Profile.

To decode Junos Telemetry Interface UDP Data at the Collector, see Decoding Junos Telemetry Interface UDP Data at the Collector.

Note:

Telemetry data is streamed directly from the source application to the collector over UDP. Therefore, the configuration is determined by the type of connection to the collector. The collector must be reachable over the management interface or a WAN interface.
In the case of line card sensors, the line cards can directly export the data to the collector if the remote address is reachable over the WAN interface. If the telemetry data must be exported over the management interface for line card sensors, it must be routed to the Routing Engine and then sent to the collector. In this scenario, configure the following hidden knob:
```
set services analytics sensor resource_test export-to-routing-engine
```

Only the .gpb format is supported for transporting telemetry data over UDP. Below is a sample configuration to stream telemetry data over UDP for the sensor path /junos/system/linecard/interface/. Data is exported every “10” seconds to the collector with a maximum payload size of “5000” to the remote address 143.1.1.2 with port number 3026:

content_copy zoom_out_map
set services analytics streaming-server server_test remote-address 143.1.1.2 
set services analytics streaming-server server_test remote-port 3026 
set services analytics export-profile export_test local-port 0 
set services analytics export-profile export_test reporting-rate 10 
set services analytics export-profile export_test payload-size 5000 
set services analytics export-profile export_test format gpb 
set services analytics export-profile export_test transport udp 
set services analytics sensor resource_test server-name server_test 
set services analytics sensor resource_test export-name export_test 
set services analytics sensor resource_test resource /junos/system/linecard/interface/

arrow_backward PREVIOUS Decoding Junos Telemetry Interface Data With UNIX Utilities

NEXT arrow_forward Decoding Junos Telemetry Interface UDP Data at the Collector

Junos Telemetry Interface User Guide

Streaming Telemetry Data Over UDP

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry