Junos Telemetry Interface

Enhanced memory monitoring with configurable thresholds and improved alarm validation (EX2300-C, EX3400, EX4100-24P, EX4100-24T, EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-48MP, EX4650, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, SRX2300, SRX4200, SRX4300, SRX4600, SRX4700, and SRX5800)—You can monitor system free pages and memory swap usage more efficiently to prevent issues related to memory shortages. The enhanced validation process reduces false alarm triggers. Additionally, you can set user-configurable thresholds for monitoring the virtual memory size (VSZ) of processes, with events categorized based on severity.

Use the set system monitor memory process (minor/major/critical)-event threshold <process-name> memory-limit <threshold> command to configure these thresholds. Alarms are integrated with eventd and alarmd infrastructure and can be viewed using the show system alarms command. To view jsysmond events, use the show system monitor memory events all command.

[See https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/command/show-system-monitor-memory-events.html.]

Enhanced telemetry with multiple gRPC servers and multiport gRPC services (EX2300, EX2300-C, EX2300-MP, EX2300-VC, EX3400, EX3400-VC, EX4000-8P, EX4000-12P, EX4000-12T, EX4000-12MP, EX4000-24MP, EX4000-48MP, EX4000-24P, EX4000-24T, EX4000-48P, EX4000-48T, EX4100-24MP, EX4100-24P, EX4100-24T, EX4100-48MP, EX4100-48P, EX4100-48T, EX4100-F-12P, EX4100-F-12T, EX4100-F-24P, EX4100-F-24T, EX4100-F-48P, EX4100-F-48T, EX4100-H-12MP, EX4100-H-12MP-DC, EX4100-H-24F, EX4100-H-24F-DC, EX4100-H-24MP, EX4100-H-24MP-DC, EX4300-MP, EX4300VC, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48MXP, EX4400-48P, EX4400-48T, EX4400-48XP, EX4600-VC, EX4650, EX4650-48Y-VC, EX9204, EX9208, EX9214, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10004, MX10008, cSRX, SRX300, SRX320, SRX340, SRX345, SRX380, SRX1500, SRX1600, SRX2300, SRX4100, SRX4200, SRX4300, SRX4600, SRX4700, SRX5400, SRX5600, SRX5800, and vSRX 3.0)—You can configure multiple gRPC servers with distinct services, listening addresses, and ports using the Junos Telemetry Interface. This feature enhances control over service management and telemetry data collection. You can also configure TLS certificates for secure communications. Use CLI commands to set listening addresses and ports and secure communications through TLS certificates. For example, you can configure a server to listen on a specific port and serve only designated gRPC services, enhancing flexibility and security in your telemetry setup.

Use Junos telemetry interface sensors to stream infrastructure and new-component environment data —Junos OS supports these new sensors:

• Relative humidity sensor:

  /components/component[name='FPC0']/properties/property[name='moisture']/

• Two input and one output dry contact sensors:

  /components/component[name='FPC0']/properties/property[name='alarm-port-output0']/components/component[name='FPC0']/properties/property[name='alarm-port-input0']/components/component[name='FPC0']/properties/property[name='alarm-port-input1']

You can also see information about dry contact and relative humidity by using the operational mode commands show chassis environment and show chassis craft-interface.

For state sensors, see Junos YANG Data Model Explorer. For commands, see show chassis environment and show chassis craft-interface.