Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Decoupled Rendering of Telemetry Data

The Junos telemetry infrastructure separates data rendering from core application processing, enhancing system performance and scalability. Dedicated rendering applications handle telemetry data rendering, enabling originating applications to focus on primary functions. This improves efficiency, particularly during high-volume telemetry data streaming. Users may notice changes in telemetry producer names, as rendering is performed by corresponding render applications. No configuration changes are needed, and existing subscriptions remain unaffected. This enhancement aligns the telemetry framework with the updated architecture, optimizing performance and scalability for telemetry data processing and streaming.

The following table lists the sensor paths and the corresponding change in telemetry producer names:

Table 1: Producer names
Root Sensor Path Previous Producer Application

New Producer Application

/junos/events eventd eventd-native-render
/state/system/syslog/messages eventd eventd-native-render
/system/grpc-servers/grpc-server jsd jsd-openconfig-render
/state/system/services/http/servers jsd jsd-openconfig-render
/telemetry-system/subscriptions/dynamic-subscriptions/dynamic-subscription na-grpcd nagrpcd-openconfig-render
/state/system/services/http/servers/grpc/gnmi na-grpcd nagrpcd-openconfig-render
/system/state sysd sysd-openconfig-render
/system/dns sysd sysd-openconfig-render
/system/ntp sysd sysd-openconfig-render
/system/ssh-server/state sysd sysd-openconfig-render
/system/telnet-server/state sysd sysd-openconfig-render
/system/logging sysd sysd-openconfig-render
/system/aaa sysd sysd-openconfig-render