Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface)

Starting with Junos OS Release 16.1R3, the Junos Telemetry Interface supports gRPC remote procedure calls (gRPC) to provision sensors and to subscribe to and receive telemetry data on MX Series routers and PTX3000 and PTX5000 routers.

Starting with JunosOS Release 17.2R1, QFX10002, QFX10008, and QFX10016 switches, QFX5200 switches, and PTX1000 and PTX10008 routers are also supported.

Starting with Junos OS Release 17.3R1, QFX5110 switches, EX4600, EX4600-VC, and EX9200 switches and the Routing and Control Board (RCB) on PTX3000 routers are also supported.

Starting with Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensors are supported.

Starting with Junos OS Release 18.2R1, PTX10002 routers are also supported.

Starting with Junos OS Release 17.4R1, PTX10016 routers and virtual MX Series (vMX) routers are also supported.

Starting with Junos OS Release 18.1R1, QFX5210-64C switches and QFX5100 switches are also supported.

Starting with Junos OS Release 18.1R1, ON_CHANGE streaming of ARP, ND, and IP sensor information associated with interfaces is supported through gRPC for MX Series routers and PTX Series routers.

Starting with Junos OS Release 18.3R1, ON_CHANGE streaming of LLDP telemetry sensor information is supported through gRPC for MX Series and PTX Series routers.

Starting with Junos OS Release 18.3R1, QFX5120-AY and EX4650 switches are also supported.

Starting with Junos OS Release 18.4R1, EX4600 switches are also supported.

Starting with Junos OS Release 18.4R1, MX480, MX960, MX2010, MX2020, MX2008 and MX-ELM routers are also supported.

Starting in Junos OS Evolved Release 19.1R1, OpenConfig (OC) and Junos Telemetry Interface (JTI) are supported. Both gRPC APIs and the customer-facing CLI remain the same as for the Junos OS. As was standard for Junos OS, Network Agent (NA) and OC packages are part of the Junos OS Evolved image.

Starting with Junos OS Evolved 19.1R1, Packet Forwarding Engine sensors on PTX10003 routers are also supported.

Starting with Junos OS Release 19.2R1, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800, and vSRX Series Services Gateways.are supported.

Starting with Junos OS Release 19.2R1, gNMI services for streaming Packet Forwarding Engine statistics is supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches.

Starting with Junos OS Release 19.2R1, gNMI services for streaming statistics is supported on QFX5110, QFX5120, QFX5200 and QFX5210 switches.

Starting with Junos OS Release 19.3R1, gNMI services for streaming Packet Forwarding Engine statistics is supported on MX240, MX480 and MX960 routers.

Starting with Junos OS Release 19.3R1, gNMI services for streaming and ON_CHANGE export of Routing Engine statistics is supported on MX960, MX2010, MX2020, PTX5000, PTX1000, and PTX10000 routers.

Starting with Junos OS Release 19.3R1, gRPC service for exporting statistics is supported on MX Series routers hosting MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards. The resource paths /junos/system/linecard/cpu/memory/, /junos/system/linecard/npu/memory/, and /junos/system/linecard/npu/utilization/ can be updated to call out individual sensors (leaves) and their respective paths for better clarity.

Starting with Junos OS Evolved Release 19.3R1, gRPC service for exporting statistics is supported on QFX5220-128C and QFX5220-32CD switches.

Starting with Junos OS Release 19.4R1, gRPC service for streaming Packet Forwarding Engine and Routing Engine statistics is supported on EX4300-MP switches.

Starting with Junos Release 20.R1, gNMI service for streaming telemetry sensors for Packet Forwarding Engine statistics is supported on MX2K-MPC11E line cards on MX2010 and MX2020 routers.

Starting with Junos OS Evolved Release 20.2R1, gRPC service for streaming NDP statistics is supported on PTX10001 routers.

Starting with Junos OS Release 20.2R1, gRPC service for streaming Packet forwarding Engine and Routing Engine statistics is supported on EX2300, EX2300-MP, and EX3400 switches.

Starting with Junos OS Release 20.2R1, gRPC service for streaming BGP routing information base (RIB) and BGP peer statistics is supported on any platform family that supports containerized routing protocol process (cRPD). cRPD is Juniper’s routing protocol process (rpd) decoupled from Junos OS and packaged as a Docker container to run in Linux-based environments.

Starting with Junos OS Release 20.2R1, ON_CHANGE BGP peer statistics export using gRPC services and gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000, PTX10000 routers and QFX5100 and QFX5200 switches.

Starting with Junos OS Release 20.2R1, streaming BGP global, peer and perr groups statistics using gRPC services is supported on EX2300, EX3400, EX4300, EX4600, and EX9200 switches.

Starting with Junos OS Release 20.2R1, streaming revenue interface statistics through Packet Forwarding Engine sensors and pseudo interface statistics through Routing Engine sensors using gRPC services and gNMI services is supported on SRX5400, SRX5600, and SRX5800 Services Gateways..

Starting with Junos OS Release 20.2R1 sensors to stream standby Routing Engine statistics are supported on MX480, MX960, MX10003, MX2010, and MX2020 routers.

Starting with Junos OS Release 20.2R1 sensors to stream EVPN statistics using gRPC services are supported with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.

Starting with Junos OS Release 20.2R1, gRPC service for exporting LDP and mLDP statistics is supported on MX Series routers.

Starting with Junos OS Release 20.3R1, gRPC service for exporting LDP and mLDP statistics is supported on MPC10E-10C-MRATE, MPC10E-15C-MRATE, and MX2K-MPC11E line cards.

See Table 1 for information about which sensors are supported with gRPC and on which platforms.

See Table 2 for a description of supported broadband edge (BBE) gRPC sensors, which are supported on all platforms supporting gRPC unless otherwise noted.

You can also use the Telemetry Explorer tool to search for and view information about telemetry sensors.

To activate a sensor, use the corresponding resource path. Each resource path enables data streaming for the system resource globally, that is, systemwide. You can also modify each resource path, such as to specify a specific logical or physical interface. For example, to specify a specific interface, include the following at the end of the path: [name='interface-name']/

Supported gRPC and gNMI Sensors

See Table 1 for a description of supported gRPC and gNMI sensors and Table 2 for a description of supported broadband edge (BBE) gRPC sensors, including the subscription path you use to provision the sensors.

Starting with Junos OS Release 20.1R1, the on-device gRPC framework is upgraded to version v1.18.0 and is applicable to both JET and JTI. This version includes important enhancements for gRPC. Earlier legacy Junos OS platform versions (non-Occam) will continue to use version v1.3.0.

Starting with Junos OS Release 20.2R1, JTI supports MX routers with dual Routing Engines or MX Series Virtual Chassis on all Packet Forwarding Engine and Routing Engine sensors currently supported on MX Series routers. The level of sensor support currently available for MX Series routers applies, whether through streaming or ON_CHANGE statistics export, using UDP, remote procedure call (gRPC) services or gRPC Network Management Interface (gNMI) services. Additionally, JTI operational mode commands will provide details for all Routing Engines and MX Series Virtual Chassis, too.

Table 1: gRPC Sensors
resource path	Description
`/bgp-rib/`	Sensor for BGP routing information base (RIB). Periodic streaming using gRPC services is supported on any platform family that supports containerized routing protocol process (cRPD) starting with Junos OS Release 20.2R1. cRPD is Juniper’s routing protocol process (rpd) decoupled from Junos OS and packaged as a Docker container to run in Linux-based environments.
`/bgp-rib/afi-safis/afi-safi/`	Sensor for BGP routing information base (RIB). Periodic streaming using gRPC services is supported on PTX10003 starting with Junos OS Release 20.2R1. You can also add the following endpoints to `/bgp-rib/afi-safis/afi-safi/`: /`ipv4-unicast/loc-rib` `ipv6-unicast/loc-rib/` `ipv6-unicast/neighbors/` `ipv4-unicast/neighbors/`
`/components/component/`	Sensor for chassis components. ON_CHANGE notification is triggered if a component (FPC) is inserted or removed or if a component’s power is on or off (FPC is online or offline). Instant reporting of such events is handled with this sensor. ON_CHANGE streaming is supported on MX960, MX2010, MX2020, PTX-5000, PTX1000, and PTX10000 routers starting with Junos OS Release 18.4R1. Starting with Junos OS Release 19.1R1, periodic streaming on QFX10002 switches and PTX10002 routers is supported. Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported. Starting with Junos OS Release 19.4R1, ON_CHANGE statistics using gRPC services or gNMI services with MX960 routers is supported. Previously, these sensors were only supported to stream statistics. Starting with Junos OS Release 20.1R1, ON_CHANGE statistics using gNMI services with MX960, MX2020, PTX1000, and PTX5000 routers. These routers support OpenConfig model: openconfig-platform.yang: oc-ext:openconfig-version 0.12.1 Starting with Junos OS Release 20.2R1, streaming pseudo interface statistics through Routing Engine sensors is supported using gRPC services or gNMI services with SRX5400, SRX5600, and SRX5800 Service Gateways. Previously, streaming statistics was only supported through gRPC services. You can also add the following endpoints to the path to stream specific statistics: `name` `state/id` `state/description` `state/serial-no` `state/part-no` The `state/type` identifies the ON_CHANGE event type. Event types are: `FRU_ADD`, `FRU_REMOVE`, `FRU_POWERON`, and `FRU_POWEROFF` For more information about ON_CHANGE statistics, see Understanding OpenConfig and gRPC on Junos Telemetry Interface.
`/components/component/cpu/`	Individual process level information sensor. Use this sensor to stream CPU usage per process statistics that are similar to output from the `show system process detail` operational mode command. Starting in Junos OS Release 20.2R1, streaming statistics using gRPC services or gNMI services on MX960, MX2010, MX2020, PTX1000, PTX5000, and PTX10000 routers QFX5100, and QFX5200 switches is supported.
`/components/component/subcomponents/subcomponent[name='FPCid:NPUid’ ]/properties/property/[name=’ counter’]/state/value`	Sensor for packet forwarding engine statistics. The subcomponent name `npu-id` refers to the number of the packet forwarding engine. This sensor provides visibility into packet forwarding engine errors and drops. Supported on MX Series routers and PTX Series routers starting with Junos OS Release 17.4R1.MX960\|MX2010\|MX2020\|PTX-5000\|PTX1000\|PTX10000 The value for `counter` is one of the following; `lts-hw-input-drops` `hwds-normal` `hwds-fabric` `hwds-info-cell` `hwds-timeout` `hwds-truncated-key` `hwds-bits-to-test` `hwds-stack-underflow` `hwds-stack-overflow` `hwds-inet6-bad-route` `hwds-inet-bad-route` `hwds-filter-discard` `hwds-dlu-not-routable` `hwds-data-error` `hwds-extended` `hwds-invalid-iif` `hwds-input-checksum` `hwds-output-mtu` `lts-input-packets` `lts-output-packets` `lts-sw-input-control-drops` `lts-sw-input-high-drops` `lts-sw-input-medium-drops` `lts-sw-input-low-drops` `lts-sw-output-low-drops`
`/components/component/subcomponents/subcomponent[name='FPCID:CCid’ ]/properties/property/[name=’ counter’]/state/value`	Sensor for packet forwarding engine statistics. The subcomponent name `cc-id` refers to the center chip. This sensor provides visibility into packet forwarding engine errors and drops. Supported on MX Series routers and PTX Series routers starting with Junos OS Release 17.4R1. The value for `counter` is one of the following; `ts-fabric-input-pps` `ts-fabric-output-pps` `ts-fabric-input-packets` `ts-fabric-output-packets` `lpbk-packets` `lpbk-pps` `lpbk-bytes` `lpbk-pps` `lpbk-drop-packets` `lpbk-drop-pps` `lpbk-drop-bytes` `lpbk-drop-bps`
`/components/component/subcomponents/subcomponent[name='FPCID’]/properties/property/[name=’ counter’]/state/value`	Sensor for packet forwarding engine statistics. The subcomponent name `FPCid` refers to the number of the Flexible PIC Concentrator. This sensor provides visibility into packet forwarding engine errors and drops. This sensor pulls CPU counters. Supported on MX Series routers and PTX Series routers starting with Junos OS Release 17.4R1. The value for `counter` is one of the following; `lts-hw-input-drops` `lts-input-packets` `lts-output-packets` `lts-sw-input-control-drops` `lts-sw-input-high-drops` `lts-sw-input-medium-drops` `lts-sw-input-low-drops` `lts-sw-output-low-drops`
`/components/component[name='CB0’]/properties/property[name=’state’/`	Sensor for Control Board (CB) state information. This information can also be found using the operational mode command `show chassis hardware`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='CB0’]/properties/property[name=’manufacture-date’/`	Sensor for Control Board (CB) manufacturing date information. This information can also be found using the operational mode command `show chassis hardware extensive`. Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers are supported.
`/components/component[name='PDU0’]/properties/property[name=’state’/`	Sensor for power distribution units (PDUs) state information. This information can also be found using the operational mode command `show chassis environment`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='PDU0’]/properties/property[name=’fru-model-number’/`	Sensor for field-replaceable unit (FRU) for a power distribution unit (PDU). This information can also be found using the operational mode command `show chassis hardware models`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='PDU0’]/properties/property[name=’manufacture-date’/`	Sensor for a power distribution unit (PDU) manufacturing date. This information can also be found using the operational mode command `show chassis hardware extensive`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='FPM Board’]/properties/property[name=’state’/`	Sensor for state information for a craft interface (FPM). This information can also be found using the operational mode command `show chassis hardware models`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='FPM Board’]/properties/property[name=’fru-model-number’/`	Sensor for field-replaceable unit (FRU) for a craft interface (FPM). This information can also be found using the operational mode command `show chassis hardware models`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='FPM Board’]/properties/property[name=’manufacture-date’/`	Sensor for a craft interface (FPM) manufacturing date. This information can also be found using the operational mode command `show chassis hardware extensive`. Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers are supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='SIB0’]/properties/property[name=’state’/`	Sensor for Switch Interface Boards (SIBs). `SIB0` and `SIB1` are supported. This information can also be found using the operational mode command `show chassis sibs`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='FPC0’]/properties/property`	Sensor for the Flexible PIC Concentrator (FPC). This information can also be found using the operational mode command `show chassis fpc detail`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported. You can also add the following as the end path: `[name=’state’/` `[name=’manufacture-date’/` `[name=’uptime’/` `[name=’Ambient Temp. EXHAUST’]` Note: This information can also be found using the operational mode command `show chassis environment fpc`. `[name=’Ambient Temp. INLET’]` Note: This information can also be found using the operational mode command `show chassis environment fpc`. `[name=’fru-model-number’]` Note: This information can also be found using the operational mode command `show chassis harware models`.
`/components/component[name='FPC0:PIC0’]/properties/property`	Sensor for the physical interface card (PIC). This information can also be found using the operational mode command `show chassis pic fpc-slot slot-num pic-slot slot-num`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported. You can also add the following as the end path: `[name=’state’/` `[name=’uptime’/`
`/components/component[name='Routing Engine 0’]/properties/property[name=’state’/`	Sensor for the routing engine state. This information can also be found using the operational mode command `show chassis environment routing-engine`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Routing Engine 0’]/properties/property[name=’mastership-state’/`	Sensor for the routing engine primary status. This information can also be found using the operational mode command `show chassis routing-engine`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Routing Engine 0’]/properties/property[name=’mastership-priority’/`	Sensor for the routing engine primary-role election priority. This information can also be found using the operational mode command `show chassis routing-engine`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Routing Engine 0’]/properties/property[name=’Ambient Left’/` `/components/component[name='Routing Engine 0’]/properties/property[name=’Ambient Right’/`	Sensor for the routing engine ambient temperature, both left and right. This information can also be found using the operational mode command `show chassis environment routing-engine`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Routing Engine 0’]/properties/property[name=’firmware_rev’/`	Sensor for the routing engine’s firmware revision. This information can also be found using the operational mode command `show chassis routing-engine bios`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Routing Engine 0’]/properties/property[name=’CPU Temperature’/`	Sensor for the routing engine’s CPU temperature. This information can also be found using the operational mode command `show chassis routing-engine`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Routing Engine 0’]/properties/property[name=’memory-dram-used’/` `/components/component[name='Routing Engine 0’]/properties/property[name=’memory-utilization-buffer’/`	Sensors for the routing engine’s memory utilization. This information can also be found using the operational mode command `show chassis routing-engine`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Routing Engine 0’]/properties/property[name=’cpu-utilization-user’/` `/components/component[name='Routing Engine 0’]/properties/property[name=’cpu-utilization-background’/` `/components/component[name='Routing Engine 0’]/properties/property[name=’cpu-utilization-kernel’/` `/components/component[name='Routing Engine 0’]/properties/property[name=’cpu-utilization-interruot’/` `/components/component[name='Routing Engine 0’]/properties/property[name=’cpu-utilization-idle’/`	Sensors for the routing engine’s CPU utilization. This information can also be found using the operational mode command `show chassis routing-engine`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Routing Engine 0’]/properties/property[name=’uptime’/`	Sensor for routing engine `uptime`. This information can also be found using the operational mode command `show chassis routing-engine`. Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers are supported.
`/components/component[name='Routing Engine 0’]/properties/property[name=’reboot-reason’/`	Sensor for the cause of a routing engine reboot. This information can also be found using the operational mode command `show chassis routing-engine`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Routing Engine 0’]/properties/property[name=’manufacture-date’/`	Sensor for the manufacture date of a routing engine. This information can also be found using the operational mode command `show chassis routing-engine`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Fan Tray0’]/properties/property[name=’state’/`	Sensor for the fan tray. This information can also be found using the operational mode command `show chassis environment`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Fan Tray0’]/properties/property[name=’fru-model-number’/`	Sensor for the fan tray model number. This information can also be found using the operational mode command `show chassis hardware models`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='Fan Tray0’]/properties/property[name=’manufacture-date’/`	Sensor for the manuafacture date of the fan tray. This information can also be found using the operational mode command `show chassis hardware models`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[name='PDU0:PSM0’]/properties/property[name=’state’/`	Sensor for the Power Distribution Module (PDU) status. This information can also be found using the operational mode command `show chassis environment`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[’Chassis’]/properties/property[name=’state’/`	Sensor for the chassis state. The chassis state is always `ONLINE`. This information can also be found using the operational mode command `show chassis environment`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component[’PSM2’]/properties/property[name=’fru-model-number’/` `/components/component[’PSM2’]/properties/property[name=’manufacture-date’/` `/components/component[’PSM2’]/properties/property[name=’Temperature’/` `/components/component[’PSM2’]/properties/property[name=’state’/`	Sensors for the power supply module (PSM) FRU model number, manufacture date, temperature, and state. This information can also be found using the operational mode command `show chassis environment`. Starting in Junos OS Evolved Release 19.1R1, periodic streaming using gRPC services on PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/components/component/properties/property/state/value`	Sensor for chassis components. Starting with Junos OS Release 19.2R1, periodic streaming using gNMI services is supported on QFX5110, QFX5120, QFX5200 and QFX5210 switches.
`/components/component/state`	Sensor for chassis component state. Starting with Junos OS Release 19.2R1, periodic streaming using gNMI services is supported on QFX5110, QFX5120, QFX5200 and QFX5210 switches.
`/components/component/transceiver/`	Sensor for transceiver diagnostics. This feature supports OpenConfig transceiver model openconfig-platform-transceiver.yang 0.5.0. Shown below, statistics are exported for FPC19. Multiples FPCs are supported. The component values and property values are names (like interface names). Starting with Junos OS Release 19.4R1, ON_CHANGE statistics are supported using gRPC services or gNMI services is supported on MX960, MX2010, MX2020, PTX1000, and PTX5000 routers and the PTX10000 line of routers. The following statistics are exported:: `components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/vendor` `components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/sonet-sdh-compliance-code` `components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/serial-no` `components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/present` `components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/output-power/instant` `components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/otn-compliance-code` `components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/laser-bias-current/instant` `components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/input-power/instant` `/components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/form-factor-preconf` `/components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/form-factor` `/components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/ethernet-pmd-preconf` `/components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/ethernet-pmd` `/components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/enabled` `/components/component[name='FPC19:PIC1:PORT11:Xcvr0']/transceiver/state/date-code`
`/junos/chassis/aggregated-devices`	Sensor for kernel link aggregation group (LAG) information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/chassis/aggregated-devices/: `ae-lp-link-down-cnt` `ae-unstack-cnt` `ps-ifl-ccc-down-cnt` `ps-lt-unstack-cnt` `rlt-lp-link-down-cnt`
`/junos/chassis/gres`	Sensor for graceful Routing Engine switchover (GRES) information. Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported. You can also add the following as the end path for /junos/chassis/gres/: `configured-state` `error-state` `gres-time` `is-protocol-master` `master-kernel-ready` `other-re-present` `other-re-alive` `slave-connect-time` `slave-kernel-ready`
`/junos/chassis/issu/`	Sensor for in-service software upgrade (ISSU) information. Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported. You can also add the following as the end path for /junos/chassis/issu/: `failure-stage` `current-issu-stage`
/junos/events	System events sensor. Starting with Junos OS Release 18.1R1, this sensor corresponds to system log messages (syslog). Starting with Junos OS Release 19.2R1, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800 and vSRX are also supported. Starting with Junos OS Release 20.2R1, streaming pseudo interface statistics through Routing Engine sensors is supported using gRPC services or gNMI services with SRX5400, SRX5600, and SRX5800 Service Gateways. Previously, streaming statistics was only supported through gRPC services. The sensor must be used with an `export-profile` that has a `reporting-rate` of 0. To subscribe for specific events, you can subscribe for /junos/events/event[id=‘EVENT_NAME’] where event EVENT_NAME is the event id that you are interested in. Many event names can be found in the messages log file. Alternatively, you can subscribe to any resource path.
`/junos/evpn/evpn-smet-forwarding/`	Global EVPN resource counters and current usage sensor. Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/junos/evpn/l3-context/`	EVPN IP prefix sensor. Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/junos/ike-security-associations/ike-security-association/routing-instance [name=’ routing-instance-name]`	Sensor for Internet Key Exchange (IKE) security statistics. When you configure a subscription request, use the `reporting-interval` parameter to configure the interval (in seconds) in which statistics are reported. Starting with Junos OS Release 18.1R1, MX Series routers are supported. `remote-ip` `local-ip` `number-ipsec-sa-created` `number-ipsec-sa-deleted` `number-ipsec-sa-rekey` `exchange-type` `in-bytes` `in-packets` `out-bytes` `out-packets` `delete-payload-received` `delete-payload-transmitted` `dpd-request-payload-received` `dpd-request-payload-transmitted` `dpd-response-payload-received` `dpd-response-payload-transmitted` `dpd-response-payload-missed` `dpd-response-payload-maximum-delay` `dpd-response-seq-payload-missed` `invalid-spi-notify-received` `invalid-spi-notify-transmitted` `routing-instance`
`/junos/kernel/multicast/`	Sensor for kernel IP multicast information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/kernel/multicast/: `iifmismatch-err-cnt` `rslv-req-err-cnt`
`/junos/kernel/peer-infra/`	Sensor for PFEMAN connection information. Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported. You can also add the following as the end path for /junos/kernel/peer-infra/: `pfeman-conn-drops` `spurious-ppt-wkups`
`/junos/kernel/record-meta-data/record_time`	Sensor for system time at which Routing Engine metadata is created. Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported.
`/junos/kernel/tcpip/arp`	Sensor for kernel Address Resolution Protocol (ARP) cache information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/kernel/tcpip/arp/: `nbrcache-iri-max` `nbrcache-mgmt-max` `nbrcache-public-max` `nbrcache-iri-cnt` `nbrcache-mgmt-cnt` `nbrcache-public-cnt` `nbrcache-iri-drop-cnt` `nbrcache-mgmt-drop-cnt` `nbrcache-public-drop-cnt`
`/junos/kernel/tcpip/ndp`	Sensor for kernel Neighbor Discovery Protocol (NDP) information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/kernel/tcpip/ndp/: `nbrcache-iri-max` `nbrcache-mgmt-max` `nbrcache-public-max` `nbrcache-iri-cnt` `nbrcache-mgmt-cnt` `nbrcache-public-cnt` `nbrcache-iri-drop-cnt` `nbrcache-mgmt-drop-cnt` `nbrcache-public-drop-cnt`
`/junos/kernel/tcpip/netisr`	Sensor for kernel NETISR network queue information for IPv4, IPv6, ARP, and Ethernet. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/kernel/tcpip/netisr/: `ether-wm-cnt` `ether-drop-cnt` `ether-pkt-queued` `ether-pkt-handled` `ip-wm-cnt` `ip-drop-cnt` `ip-pkt-queued` `ip-pkt-handled` `ip6-wm-cnt` `ip6-drop-cnt` `ip6-pkt-queued` `ip6-pkt-handled` `arp-wm-cnt` `arp-drop-cnt` `arp-pkt-queued` `arp-pkt-handled`
`/junos/kernel/tcpip/nhidx`	Sensor for kernel nexthop index space exhaustion information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/kernel/tcpip/nhdix/: `nexthop-pvt-max` `nexthop-pub-max` `nexthop-pvt-cnt` `nexthop-pub-cnt`
`/junos/kernel/tcpip/rtb`	Sensor for kernel route table information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/kernel/tcpip/rtb/: `route-clone-cnt` `route-clone-max`
`/junos/kernel/tcpip/rtstock`	Sensor for kernel routing table socket (RTSOCK) information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/kernel/rtsock/: `total-error-cnt` `total-veto-cnt`
`/junos/kernel/tcpip/tcp`	Sensor for kernel Transport Control Protocol (TCP) information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/kernel/tcpip/tcp/: `tcp-ddos-attack-cnt` `tcp-conndrops-cnt` `tcp-time-wait-conn`
`/junos/kernel/tnp/`	Sensor for kernel Trivial Network Protocol (TNP) information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/kernel/tnp/: `tnp-frag-drop-cnt` `tnp-hello-drop-cnt`
`/junos/kernel/tunnel/`	Sensor for kernel Reverse Path Forwarding (RPF) and non-RPF tunnel information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/kernel/tunnel/: `looped-cnt` `nonrpf-tunnelid-cnt` `nonrpf-tunnelid-max` `rpf-tunnelid-cnt` `rpf-tunnelid-max`
`/junos/kernel/vpls/`	Sensor for kernel Virtual Private LAN Service (VPLS) information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/kernel/vpls/: `flood-token-cnt` `flood-token-max` `unicast-token-cnt` `unicast-token-max`
`/junos/kernel-ifstate`	Sensor for Routing Engine ifstate information. Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported. You can also add the following as the end path for /junos/kernel-ifstate/: `alive-clients-cnt` `alive-ifstates-cnt` `client-limit-reached` `dead-clients-cnt` `dead-ifstates-cnt` `delayed-unrefs-cnt` `delayed-unrefs-max` `stuck-clients-cnt`
`/junos/kernel-ifstate/stats/churn-rate`	Sensor for Routing Engine network object churn rate statistics. Starting in Junos OS Release 18.2R1, MX Series and PTX Series switches are supported. `overall-churn-rate` `route-add-rate` `route-change-rate` `route-delete-rate` `nexthop-add-rate` `nexthop-change-rate` `nexthop-delete-rate`
`/junos/kernel-ifstate/stats/peer-consumption-rate`	Sensor for Routing Engine network object peer consumption rate statistics. Starting in Junos OS Release 18.2R1, MX Series and PTX Series switches are supported. `peer-index` `consumption-rate-counter` `consumption-route-add-rate` `consumption-route-delete-rate` `consumption-nexthop-add-rate` `consumption-nexthop-change-rate` `consumption-nexthop-delete-rate`
`/junos/kernel-ifstate/stats/record-seq-num`	Sequence number of a statistic or record.
`/junos/kernel-ifstate/stats/record-time`	System time at which a statistic or record is created.
`/junos/kernel-ifstate/stats/vetos-statistics`	Sensor for Routing Engine state statistics. Starting in Junos OS Release 18.2R1, MX Series and PTX Series switches are supported. `veto-vm-page-count-severe` `veto-ifstate-memory` `veto-memory-overconsumed` `veto-pfe-veto-max-routes` `veto-too-many-delayed-unrefs` `veto-nh-memory-usage` `veto-mbuf-cluster` `veto-flabel-space-exhaustion` `veto-flabel-space-consumption`
`/junos/routing-options/nonstop-routing`	Sensor for kernel Non-Stop Routing (NSR) Junos Socket Replication (JSR) information. Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported. You can also add the following as the end path for /junos/routing-options/nonstop-routing/: `jsr-split-failure-cnt` `jsr-merge-failure-cnt` `jsr-prl-queue-full-cnt`
`/junos/rpm/probe-results/probe-test-results/`	Sensor for probe test results for Real time Performance Monitoring (RPM) statistics. These statistics provide RPM monitoring data results collected by Juniper devices. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering. Starting with Junos OS Release 18.3R1, MX Series routers are supported. The following end paths are also supported for the resource path: `owner` `test-name` `target-address` `target-url` `source-address` `destination-interface` `probe-type` `icmp-id` `routing-instance-name` `test-size` `http-status` `loss-thresh-total` `loss-thresh-succ` `rtt-thresh` `rtt-jitter-thresh` `rtt-stddev-thresh` `igr-thresh` `igr-jitter-thresh` `igr-stddev-thresh` `egr-thresh` `egr-jitter-thresh` `egr-stddev-thresh` `probe-tests-hw-ts-err/invalid-client-recv-ts-cntr` `probe-tests-hw-ts-err/invalid-client-nots-cntr` `probe-tests-hw-ts-err/invalid-server-send-ts-cntr` `probe-tests-hw-ts-err/invalid-server-spent-time-cntr` `probe-single-results` `probe-single-results/probe-time` `probe-single-results/probe-sent-time` `probe-single-results/probe-status` `probe-single-results/hardware-timestamp-status` `probe-single-results/rtt` `probe-single-results/egress` `probe-single-results/ingress` `probe-single-results/round-trip-jitter` `probe-single-results/egress-jitter` `probe-single-results/round-trip-interarrival-jitter` `probe-single-results/egress-interarrival-jitter` `probe-single-results/ingress-interarrival-jitter` `probe-test-generic-result` `probe-test-generic-results/results-scope` `probe-test-generic-results/probes-sent` `probe-test-generic-results/probe-responses` `probe-test-generic-results/loss-percentage` `probe-test-generic-measurements` `probe-test-generic-measurements/samples` `probe-test-generic-measurements/min-delay` `probe-test-generic-measurements/max-delay` `probe-test-generic-measurements/avg-delay` `probe-test-generic-measurements/jitter-delay` `probe-test-generic-measurements/stddev-delay` `probe-test-generic-measurements/sum-delay`
`/junos/npu/memory`	Starting with Junos OS Release 19.1R1, periodic streaming on QFX10002 switches and PTX10002 routers is supported.
`/junos/rpm/history-results/history-single-test-results/`	Sensor for history results for Real time Performance Monitoring (RPM) statistics. These statistics provide RPM monitoring data results collected by Juniper devices. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering. Starting with Junos OS Release 18.3R1, MX Series routers are supported. The following end paths are also supported for the resource path: `owner` `test-name` `target-address` `target-url` `source-address` `destination-interface` `probe-type` `icmp-id` `test-size` `http-status` `routing-instance-name` `loss-thresh-total` `loss-thresh-succ` `rtt-thresh` `rtt-jitter-thresh` `rtt-stddev-thresh` `igr-thresh` `igr-jitter-thresh` `igr-stddev-thresh` `egr-thresh` `egr-jitter-thresh` `egr-stddev-thresh` `probe-single-results` `probe-single-results/probe-time` `probe-single-results/probe-sent-time` `probe-single-results/probe-status` `probe-single-results/hardware-timestamp-status` `probe-single-results/rtt` `probe-single-results/egress` `probe-single-results/ingress` `probe-single-results/round-trip-jitter` `probe-single-results/egress-jitter` `probe-single-results/ingress-jitter` `probe-single-results/round-trip-interarrival-jitter` `probe-single-results/egress-interarrival-jitter` `probe-single-results/ingress-interarrival-jitter`
`/junos/rpm/server/`	Sensor for server results for Real time Performance Monitoring (RPM) statistics. These statistics provide RPM monitoring data results collected by Juniper devices. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering. Starting with Junos OS Release 18.3R1, MX Series routers are supported. The following end paths are also supported for the resource path: `active-servers` `active-servers/protocol` `active-servers/port` `active-servers/dst-interface`
`/junos/security/veriexec-state`	Sensor for Veriexec state information. Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported.
/junos/services/health-monitor/config/	Sensor for the health monitoring configuraiton. Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.
/junos/services/health-monitor/data/	Sensor for health monitoring data. Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.
`/junos/services/ip-tunnel[name='tunnel-name']/usage/counters[name='counter-name']/`	Sensor for Packet Forwarding Engine dynamic tunnels statistics. The statistics are used to report various network element performance metrics in a scalable and efficient way, providing visibility into Packet Forwarding Engine errors and drops. A timestamp indicating when the counters were last reset is included with all the exported data to allow collectors to determine if and when a reset event happened; for example, if the Packet Forwarding Engine hardware restarted. Exported statistics are similar to the output of the operational mode command `show nhdb hw dynamic-ip-tunnels`. Starting with Junos OS Release 17.4R1, MX Series devices are supported on gRPC services, with the exception of MX80 and MX104 routers. These routers support UDP export only for this sensor. To configure UDP export, include the sensor `/junos/services/ip-tunnel/usage/` in the sensor (Junos Telemetry Interface) configuration statement at the [`edit services analytics`] hierarchy level.
`/junos/services/label-switched-path/usage/`	Sensor for LSP statistics. On MX Series routers only, the following are also supported: bidirectional LSPs for ultimate-hop popping (UHP). Starting with Junos OS Release 17.2R1, QFX10000 switches and PTX1000 routers are also supported. Starting with Junos OS Release 17.3R1, EX9200 switches are also supported. Starting with Junos OS Release 17.4R1 on MX Series and PTX Series routers only, statistics for bypass LSPs are also exported. Previously, only statistics for ingress LSPs were exported. Starting with Junos OS Release 18.2R1, QFX5100, QFX5110, and QFX5200 switches are also supported. Starting with Junos OS Release 18.3R1, QFX5120-48Y and EX4650 switches are also supported. Starting with Junos OS Release 18.4R1, EX4600 switches are also supported. Starting with Junos OS Release 19.1R1, PTX10001-20C routers support RSVP bypass LSPs originating at the transit node Starting with Junos OS Release 19.1R1, periodic streaming on QFX10002 switches and PTX10002 routers is supported. Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers are supported. Starting with Junos OS Release 19.2R1, ACX6360 routers are supported. Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services. Supported on QFX5200 switches starting with Junos OS Release 19.2R1 for streaming telemetry information using gNMI services. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported. Starting with Junos OS Evolved Release 20.2R1, periodic streaming using gRPC services with PTX10001 routers is supported. For bypass LSPs, the following are exported: Bypass LSP originating at the ingress router of the protected LSP. Bypass LSP originating at the transit router of the protected LSP. Bypass LSP protecting the transit LSP as well as the locally originated LSP. When the bypass LSP is active, traffic is exported both on the bypass LSP and the ingress (protected) LSP. Note: When you enable a sensor for LSP statistics only, you must also configure the `sensor-based-stats` statement at the `[edit protocols mpls]` hierarchy level. MX Series routers should operate in enhanced mode. If not enabled by default, include either the `enhanced-ip` statement or the `enhanced-ethernet` statement at the `[edit chassis network-services]` hierarchy level.
`/junos/twamp/client/control-connection/`	Sensor for client control connection results for Two-Way Active Management Protocol (TWAMP). TWAMP (described in RFC 5357). Used to measure traffic performance between end-points, you can use this information to assure service level agreements, improve network design, and optimize traffic engineering. Starting with Junos OS Release 18.3R1, MX Series routers are supported. The following end paths are also supported for the resource path: `control-name` `client-address` `client-port` `server-address` `server-port` `session-count` `auth-mode` `server-address` `server-port` `test-session/session-name` `test-session/sender-address` `test-session/sender-port` `test-session/reflector-address` `test-session/reflector-port`
`/junos/twamp/client/probe-test-results/`	Sensor for client probe test results for Two-Way Active Management Protocol (TWAMP). TWAMP (described in RFC 5357) is used to measure traffic performance between end-points. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering. Starting with Junos OS Release 18.3R1, MX Series routers are supported. The following end paths are also supported for the resource path: `owner` `test-name` `destination-interface` `test-size` `server-address` `server-port` `client-address` `client-port` `reflector-address` `reflector-port` `sender-address` `sender-port` `loss-thresh-total` `loss-thresh-succ` `rtt-thresh` `rtt-jitter-thresh` `rtt-stddev-thresh` `igr-thresh` `igr-jitter-thresh` `igr-stddev-thresh` `egr-thresh` `egr-jitter-thresh` `egr-stddev-thresh` `probe-tests-hw-ts-err/invalid-client-recv-ts-cntr` `probe-tests-hw-ts-err/invalid-client-nots-cntr` `probe-tests-hw-ts-err/invalid-server-send-ts-cntr` `probe-tests-hw-ts-err/invalid-server-spent-time-cntr` `probe-single-results/` `probe-single-results/probe-time` `probe-single-results/probe-sent-time` `probe-single-results/probe-status` `probe-single-results/hardware-timestamp-status` `probe-single-results/rtt` `probe-single-results/egress` `probe-single-results/ingress` `probe-single-results/round-trip-jitter` `probe-single-results/egress-jitter` `probe-single-results/ingress-jitter` `probe-single-results/round-trip-interarrival-jitter` `probe-single-results/egress-interarrival-jitter` `probe-single-results/ingress-interarrival-jitter` `probe-test-generic-results/` `probe-test-generic-results/results-scope` `probe-test-generic-results/probes-sent` `probe-test-generic-results/probe-responses` `probe-test-generic-results/loss-percentage` `probe-test-generic-results/probe-test-rtt` `probe-test-generic-results/probe-test-generic-measurements/` `probe-test-generic-results/probe-test-generic-measurements//probe-measurement-type` `probe-test-generic-results/probe-test-generic-measurements/samples` `probe-test-generic-results/probe-test-generic-measurements/min-delay` `probe-test-generic-results/probe-test-generic-measurements/max-delay` `probe-test-generic-results/probe-test-generic-measurements/avg-delay` `probe-test-generic-results/probe-test-generic-measurements/jitter-delay` `probe-test-generic-results/probe-test-generic-measurements/stddev-delay` `probe-test-generic-results/probe-test-generic-measurements/sum-delay`
`/junos/twamp/client/history-test-results/history-single-test-results/`	Sensor for client history test results for Two-Way Active Management Protocol (TWAMP). TWAMP (described in RFC 5357) is used to measure traffic performance between end-points. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering. Starting with Junos OS Release 18.3R1, MX Series routers are supported. `owner` `test-name` `destination-interface` `test-size` `server-address` `server-port` `client-address` `client-port` `reflector-address` `reflector-port` `sender-address` `sender-port` `loss-thresh-total` `loss-thresh-succ` `rtt-thresh` `rtt-jitter-thresh` `rtt-stddev-thresh` `igr-thresh` `igr-jitter-thresh` `igr-stddev-thresh` `egr-thresh` `egr-jitter-thresh` `egr-stddev-thresh` `probe-single-results/` `probe-single-results/probe-time` `probe-single-results/probe-sent-time` `probe-single-results/probe-status` `probe-single-results/hardware-timestamp-status` `probe-single-results/rtt` `probe-single-results/egress` `probe-single-results/ingress` `probe-single-results/round-trip-jitter` `probe-single-results/egress-jitter` `probe-single-results/ingress-jitter` `probe-single-results/round-trip-interarrival-jitter` `probe-single-results/egress-interarrival-jitter` `probe-single-results/ingress-interarrival-jitter`
`/junos/twamp/server/control-connection/`	Sensor for control connection results for servers for Two-Way Active Management Protocol (TWAMP). TWAMP (described in RFC 5357) is used to measure traffic performance between end-points. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering. Starting with Junos OS Release 18.3R1, MX Series routers are supported. `control-name` `client-address` `client-port` `server-address` `server-port` `session-count` `auth-mode` `test-session/` `test-session/session-name` `test-session/sender-address` `test-session/sender-port` `test-session/reflector-address` `test-session/reflector-port`
`/network-instances/network-instance[name='instance-name']/mpls//container-tunnels/container-tunnel[name='name']state/`	Sensor for container tunnel streaming notifications and normalization status. Starting in Junos OS Evolved Release 19.2R1, PTX10003 routers support streaming statistics. The following paths are also supported: `admin-status` `bytes` `current-path-time` `metric-type` `metric` `name` `next-reoptimization-time` `online-time` `oper-status` `path-changes` `state-changes` `counters/bytes` `counters/packets`
`/network-instances/network-instance[name='instance-name']/mpls/lsps/constrained-path/container-tunnels/container-tunnel[name='name']state/`	Sensor for container tunnel streaming notifications and normalization status. Starting with Junos OS Release 19.1R1, this sensor is supported on all platforms supporting JTI. Starting in Junos OS Evolved Release 19.2R1, PTX10003 routers are supported with the end points: `admin-status` `oper-status` The following paths are also supported: `name` `oper-state` `member-count` `minimum-lsp-count` `maximum-lsp-count` `normalize-timer` `normalize-threshold` `aggregate-bandwidth` `sampled-aggregate-bandwidth` `max-signaling-bandwidth` `min-signaling-bandwidth` `splitting-bandwidth` `merging-bandwidth` `incremental-normalization` `failover-normalization` `time-to-normalize` `sampling/sampling-outlier-cutoff` `sampling/sampling-mode` `sampling/sampling-percentile` `normalization-status` which includes `normalize-init`, `normalize-complete`, and `avoid-normalize`
`/network-instances/network-instance[name='instance-name']/mpls/lsps/constrained-path/tunnels/tunnel[name='name']/p2p-tunnel-attributes/p2p-primary-paths/p2p-primary-path[name='path-name']/lsp-instances/state/notify-status`	Sensor for LSP events and properties. LSP events and properties are exported for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs. Supported on QFX5200 switches for streaming and ON_CHANGE statistics export through gNMI services starting with Junos OS Release 19.2R1.
`/network-instances/network-instance[name='instance-name']/mpls/lsps/constrained-path/tunnels/tunnel[name='name']/p2p-tunnel-attributes/p2p-primary-paths/p2p-primary-path[name='path-name']/`	Sensor for LSP events and properties. LSP events and properties are exported for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs. Starting with Junos OS Release 19.1R1, periodic streaming on QFX10002 switches and PTX10002 routers is supported. Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported. The following paths are also supported: `lsp-instances/state/bandwidth` `lsp-instances/state/max-avg-bandwidth` `lsp-instances/state/metric` `lsp-instances/state/notify-status` `state/explicit-path-name` `state/notify-status`
`/network-instances/network-instance[name='instance-name']/mpls/lsps/constrained-path/tunnels/tunnel[name='name']/p2p-tunnel-attributes/p2p-primary-paths/p2p-primary-path[name='path-name']/`	Sensor for LSP events and properties. LSP events and properties are exported for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs. Note: Starting with Junos OS Release 17.4R1, telemetry data for LSP events and properties is reported separately for each routing instance. To export data for LSP events and properties, you must now include `/network-instances/network-instance[name='instance-name']/` in front of all supported paths. . Supported on MX Series and PTX Series routers and QFX10000 switches starting with Junos OS Release 17.2R1. Supported on EX4600 and EX9200 switches and QFX5110 and QFX5200 switches starting with Junos OS Release 17.3R1. Starting with Junos OS Release 18.1R1, QFX5100 switches are also supported. Starting with Junos OS Release 18.3R1, QFX5120-48Y and EX4650 switches are also supported. Starting with Junos OS Release 18.4R1, EX4600 switches are also supported. The following paths are also supported: `lsp-instances/state/notify-status/initiated` `lsp-instances/state/notify-status/lsp-up` `lsp-instances/state/notify-status/lsp-down` `lsp-instances/state/notify-status/lp-available` `lsp-instances/state/notify-status/lp-unavailable` `lsp-instances/state/notify-status/autobw-success` `lsp-instances/state/notify-status/autobw-fail` `lsp-instances/state/notify-status/patherr-recv` `lsp-instances/state/notify-status/tunnel-local-repaired` `lsp-instances/state/bandwidth` `lsp-instances/state/metric` `lsp-instances/state/max-avg-bandwidth` `/state/associated-rsvp-sessions/associated-rsvp-session[local-index ='index-number']/` `state/notify-status` `state/notify-status/originate-mbb` `state/notify-status/cspf-noroute` `state/notify-status/cspf-success` `state/notify-status/gr-recovery-fail` `state/explicit-path-name` Note: To specify a specific LSP name and source address, include `[name='lsp-name',source='address']` after `mpls/lsp/constrained-path-tunnels/tunnel/` in any of the supported paths. If do not include a specific LSP name, data is exported for all configured LSPs.
`/network-instances/network-instance[name='instance-name']/mpls/lsps/constrained-path/tunnels/tunnel[name='name']/p2p-tunnel-attributes/p2p-primary-paths/p2p-primary-path[name='path-name'][local-index=’local-index’]/state/notify-status`	Sensor for self-ping failure. This sensor supports self-ping logs. Starting with Junos OS Release 19.1R1, this sensor is supported on all platforms supporting JTI.
`/network-instances/network-instance[name='instance-name']/mpls/lsps/constrained-path/tunnels/tunnel[name='name']/p2p-tunnel-attributes/p2p-primary-paths/p2p-primary-path[name='path-name'][local-index=’local-index’]/state/reason/`	Sensor that indicates the reason for a self-ping failure. Starting with Junos OS Release 19.1R1, this sensor is supported on all platforms supporting JTI.
`/network-instances/network-instance[name='instance-name']/mpls/signaling-protocols/rsvp-te/sessions/session/state/notify-status/`	Starting with Junos OS Release 17.4R1, telemetry data for LSP events and properties is reported separately for each routing instance. Supported on MX Series and PTX Series routers and QFX10000 switches starting with Junos OS Release 17.2R1. Supported on EX4600 and EX9200 switches and QFX5110 and QFX5200 switches starting with Junos OS Release 17.3R1. Starting with Junos OS Release 18.1R1, QFX5100 switches are also supported. Starting with Junos OS Release 18.3R1, QFX5120-48Y and EX4650 switches are also supported. Starting with Junos OS Release 18.4R1, EX4600 switches are also supported. Starting with Junos OS Release 19.1R1, periodic streaming on QFX10002 switches and PTX10002 routers is supported. Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported. The following paths are also supported: `detour-up` `detour-down` `patherr-recv` `patherr-recv/admission_control_failure` `patherr-recv/session_preeempted` `patherr-recv/bad_loose_route` `patherr-recv/bad_strict_route` `patherr-recv/label_allocation_failure` `patherr-recv/non_rsvp_capable_router` `patherr-recv/ttl_expired` `patherr-recv/routing_loop_detected` `patherr-recv/requested_bandwidth_unavailable` `patherr-recv/ttl_expired` `pathmtu-change`
`/junos/system/cmerror/configuration`	Sensor for error monitoring configuration. Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.
`/junos/system/cmerror/counters`	Sensor for error monitoring counters. Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.
`/junos/system/linecard/bmon-sw/`	Sensor for interface burst monitoring. Starting in Junos OS Evolved Release 19.3R1, QFX5220-128C and QFX5220-32CD switches are supported for streaming statistics on gRPC services. You can also add the following to the end of the path to stream specific statistics for interface burst monitoring: `rx_bytes`-Total number of bytes received during the export interval. `tx_bytes`-Total number of bytes transmitted during the export interval. `start_ts`-Start timestamp for the data collection window. `rx_peak_byte_rate`-Maximum bytes rate per millisecond received from all the sampling intervals in the export interval. `rx_peak_ts`-Timestamp of the first burst. `tx_peak_byte_rate`-Maximum bytes rate per millisecond, transmitted from all the sampling intervals in the export interval. `tx_peak_byte_ts`-Timestamp of the first transmit burst.
`junos/system/linecard/npu/memory/`	Sensor for network processing unit (NPU) memory. Supported on MX Series routers with MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards starting with Junos OS Release 19.3R1 for exporting telemetry information using gRPC services. This feature provides a different level of exported statistics in comparison to previous releases because it use the OpenConfig AFT model. Supported on MX2010 and MX2020 routers with MX2K-MPC11E line cards starting with Junos OS Release 20.1R1 for streaming telemetry information using gRPC services. You can also add the following to the end of the path to stream specific statistics for NPU memory: `mem-util-edmem-size` `mem-util-edmem-allocated` `mem-util-edmem-utilization` `mem-util-idmem-size` `mem-util-idmem-allocated` `mem-util-idmem-utilization` `mem-util-bulk-dmem-size` `mem-util-bulk-dmem-allocated` `mem-util-bulk-dmem-utilization` `mem-util-next-hop-edmem-size` `mem-util-next-hop-edmem-allocated` `mem-util-next-hop-edmem-utilization` `mem-util-next-hop-bulk-dmem-size` `mem-util-next-hop-bulk-dmem-allocated` `mem-util-next-hop-bulk-dmem-utilization` `mem-util-next-hop-idmem-size` `mem-util-next-hop-idmem-allocated` `mem-util-next-hop-inline-services-free-count` `mem-util-next-hop-mobile:-timing-profile-bytes-allocated` `mem-util-next-hop-mobile:-timing-profile-allocation-count` `mem-util-next-hop-mobile:-timing-profile-free-count` `mem-util-next-hop-packet-reassembly-(rw)-bytes-allocated` `mem-util-next-hop-packet-reassembly-(rw)-allocation-count` `mem-util-next-hop-packet-reassembly-(rw)-free-count` `mem-util-next-hop-packet-reassembly---persistent-(rw)-bytes-allocated` `mem-util-next-hop-packet-reassembly---persistent-(rw)-allocation-count` `mem-util-next-hop-packet-reassembly---persistent-(rw)-free-count` `mem-util-next-hop-ml-bundle-bytes-allocated` `mem-util-next-hop-ml-bundle-allocation-count` `mem-util-next-hop-ml-bundle-free-count` `mem-util-next-hop-ddos-scfd-params-bytes-allocated` `mem-util-next-hop-ddos-scfd-params-allocation-count` `mem-util-next-hop-ddos-scfd-params-free-count` `mem-util-next-hop-vbf-bytes-allocated` `mem-util-next-hop-vbf-allocation-count` `mem-util-next-hop-vbf-free-count` `mem-util-next-hop-ptp-ieee-1588-nhs-bytes-allocated` `mem-util-next-hop-ptp-ieee-1588-nhs-allocation-count` `mem-util-next-hop-ptp-ieee-1588-nhs-free-count` `mem-util-next-hop-cos-bytes-allocated` `mem-util-next-hop-cos-allocation-count` `mem-util-next-hop-cos-free-count` `mem-util-next-hop-inline-hash-sessions-bytes-allocated` `mem-util-next-hop-inline-hash-sessions-allocation-count` `mem-util-next-hop-inline-hash-sessions-free-count` `mem-util-next-hop-inline-mdi-bytes-allocated` `mem-util-next-hop-inline-mdi-allocation-count` `mem-util-next-hop-inline-mdi-free-count` `mem-util-next-hop-cos-enhanced-priority-bytes-allocated` `mem-util-next-hop-cos-enhanced-priority-allocation-count` `mem-util-next-hop-cos-enhanced-priority-free-count` `mem-util-firewall-fw-bytes-allocated` `mem-util-firewall-fw-allocation-count` `mem-util-firewall-fw-free-count` `mem-util-counters-fw-counter-bytes-allocated` `mem-util-counters-fw-counter-allocation-count` `mem-util-counters-fw-counter-free-count` `mem-util-counters-fw-policer-bytes-allocated` `mem-util-counters-fw-policer-allocation-count` `mem-util-counters-fw-policer-free-count` `mem-util-counters-ifd-error-cntr-bytes-allocated` `mem-util-counters-ifd-error-cntr-allocation-count` `mem-util-counters-ifd-error-cntr-free-count` `mem-util-counters-nh-cntr-bytes-allocated` `mem-util-counters-nh-cntr-allocation-count` `mem-util-counters-nh-cntr-free-count` `mem-util-counters-ifl-cntr-bytes-allocated` `mem-util-counters-ifl-cntr-allocation-count` `mem-util-counters-ifl-cntr-free-count` `mem-util-counters-bridge-domain-counter0-bytes-allocated` `mem-util-counters-bridge-domain-counter0-allocation-count` `mem-util-counters-bridge-domain-counter0-free-count` `mem-util-counters-bridge-domain-counter0-free-count` `mem-util-counters-bridge-domain-cntr-bytes-allocated` `mem-util-counters-bridge-domain-cntr-allocation-count` `mem-util-counters-bridge-domain-cntr-free-count` `mem-util-counters-sample-inline-params-bytes-allocated` `mem-util-counters-sample-inline-params-allocation-count` `mem-util-counters-sample-inline-params-free-count` `mem-util-counters-services-counters-bytes-allocated` `mem-util-counters-services-counters-allocation-count` `mem-util-counters-services-counters-free-count` `mem-util-counters-exception-counter-bytes-allocated` `mem-util-counters-exception-counter-allocation-count` `mem-util-counters-exception-counter-free-count` `mem-util-counters-issu-policer-bytes-allocated` `mem-util-counters-issu-policer-allocation-count` `mem-util-counters-issu-policer-free-count` `mem-util-counters-ddos-scfd-counters-bytes-allocated` `mem-util-counters-ddos-scfd-counters-allocation-count` `mem-util-counters-ddos-scfd-counters-free-count` `mem-util-counters-ip-reassembly-counter-bytes-allocated` `mem-util-counters-ip-reassembly-counter-allocation-count` `mem-util-counters-ip-reassembly-counter-free-count` `mem-util-hash-hash-edmem-overhead-bytes-allocated` `mem-util-hash-hash-edmem-overhead-bytes-allocated` `mem-util-hash-hash-edmem-overhead-bytes-allocated` `mem-util-hash-hash-edmem-overhead-bytes-allocated` `mem-util-hash-hash-edmem-overhead-bytes-allocated` `mem-util-hash-hash-edmem-overhead-allocation-count` `mem-util-hash-hash-edmem-overhead-free-count` `mem-util-hash-hash-edmem-bkt-bytes-allocated` `mem-util-hash-hash-edmem-bkt-allocation-count` `mem-util-hash-hash-edmem-bkt-free-count` `mem-util-hash-hash-edmem-rec-bytes-allocated` `mem-util-hash-hash-edmem-rec-allocation-count` `mem-util-hash-hash-edmem-rec-free-count` `mem-util-hash-hash-edmem-sideband-bytes-allocated` `mem-util-hash-hash-edmem-sideband-allocation-count` `mem-util-hash-hash-edmem-sideband-free-count` `mem-util-hash-hash-dmem-bkt-bytes-allocated` `mem-util-hash-hash-dmem-bkt-allocation-count` `mem-util-hash-hash-dmem-bkt-free-count` `mem-util-hash-hash-dmem-rec-bytes-allocated` `mem-util-hash-hash-dmem-rec-allocation-count` `mem-util-hash-hash-dmem-rec-free-count` `mem-util-hash-hash-dmem-sideband-bytes-allocated` `mem-util-hash-hash-dmem-sideband-allocation-count` `mem-util-hash-hash-dmem-sideband-free-count` `mem-util-encaps-ueid-bytes-allocated` `mem-util-encaps-ueid-allocation-count` `mem-util-encaps-ueid-free-count` `mem-util-encaps-ueid-shared-bytes-allocated` `mem-util-encaps-ueid-shared-bytes-allocated` `mem-util-encaps-ueid-shared-allocation-count` `mem-util-encaps-ueid-shared-free-count` `mem-util-encaps-fabric-bytes-allocated` `mem-util-encaps-fabric-allocation-count` `mem-util-encaps-fabric-free-count` `mem-util-services-nh-inline-jflow-sample-rr-(svcs)-bytes-allocated` `mem-util-services-nh-inline-jflow-sample-rr-(svcs)-allocation-count` `mem-util-services-nh-inline-jflow-sample-rr-(svcs)-free-count` `mem-util-services-nh-inline-jflow-sample-nh-(svcs)-bytes-allocated` `mem-util-services-nh-inline-jflow-sample-nh-(svcs)-allocation-count` `mem-util-services-nh-inline-jflow-sample-nh-(svcs)-free-count`
`junos/system/linecard/npu/memory/`	Sensor for network processing unit (NPU) memory, NPU memory utilization, and total memory available for each memory type. Supported on QFX10000 switches and PTX1000 routers starting with Junos OS Release 17.2R1. Supported on EX9200 switches starting with Junos OS Release 17.3R1. Note: Starting with Junos Release 17.4R1, FPC1 and FCP2 on PTX Series routers export data for NPU memory and NPU memory utilization. Previously, this sensor was supported only on FPC 3. Starting with Junos OS Release 18.3R1, EX4650 switches are supported. Starting with Junos OS Release 19.1R1, periodic streaming on PTX10002 routers is supported. Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers and PTX1000 and PTX10000 routers are supported on gRPC and gNMI services. The OpenConfig path is `/components/component[name="FPC<fpc-id>:NPU<npu-id>"] /properties/property/` You can also add the following to the end of the path to stream specific statistics for NPU memory: `[name="mem-util-<memory-name>-size"]/value` `[name="mem-util-<memory-name>-bytes-allocated"]/value` `[name="mem-util-<memory-name>-utilization"]/value` `[name="mem-util-<partition-name>-< app-name>-allocation-count"]/value` `[name="mem-util-<partition-name>-< app-name>-bytes-allocated"]/value` `[name="mem-util-<partition-name>-< app-name>-free-count"]/value` You can also add the following to the end of the path to stream specific statistics for NPU: `[name="util-<memory-name>-average-util">/value` `[name="util-<memory-name>-highest-util">/value` `[name="util-<memory-name>-lowest-util">/value` `[name="util-<memory-name>-average-cache-hit-rate">/value` `[name="util-<memory-name>-lowest-cache-hit-rate">/value` `[name="util-<packet-identifier>-rate">/value` You can also export the following statistics for NPU memory for PTX routers only `pfe_name` `combined_pool_name` `combined_size` `combined_usage_cnt` `combined_utilization` `global_pool_name` `global_usage_cnt` `global_alloc_cnt` `global_free_cnt` `local_pool_name` `local_usage_cnt` `local_alloc_cnt` `local_free_cnt`
`/junos/system/linecard/node-slicing/af-fab-stats/`	Sensor to export abstracted fabric (AF) interface-specific load-balancing and fabric queue statistics. This sensor is only supported for in node virtualization configurations on MX routers with an AF Interface as the connecting link between guest network functions (GNFs).The sensor also reports aggregated statistics across all AF interfaces hosted on a source packet forwarding engine of local guest GNFs along with the fabric statistics for all traffic ingressing from and egressing to the fabric from that the packet forwarding engine. Supported on MX480, MX960, MX2010, MX2020, MX2008 and MX-ELM routers with Junos OS Release 18.4R1.
`/junos/system/linecard/cpu/memory/`	Sensor for CPU memory. This sensor exports the CPU and memory utilization per process and CPU usage for threads per process. The current implementation is Linux-based; therefore, the export information and gathered output format differs significantly from this sensor’s performance on previous platforms. Supported on MX Series routers with MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards starting with Junos OS Release 19.3R1 for exporting telemetry information using gRPC services. This feature provides a different level of exported statistics in comparison to previous releases because it use the OpenConfig AFT model. Supported on MX2010 and MX2020 routers with MX2K-MPC11E line cards starting with Junos OS Release 20.1R1 for streaming telemetry information using gRPC services. Supported on EX2300, EX2300-MP, and EX3400 switches starting with Junos OS Release 20.2R1 and later for streaming telemetry information using gRPC services. Supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1 and later for INITIAL_SYNC statistics using gNMI services. The statistics exported from this sensor are found in the following operational mode commands: `show system info`, `show system processes`, and `show system cpu`.
`/junos/system/linecard/cpu/memory/`	Sensor for CPU memory. Note: On PTX Series routers, FPC1 and FPC2 are not supported. Supported on QFX10000 switches and PTX1000 routers starting with Junos OS Release 17.2R1. Supported on EX9200 switches starting with Junos OS Release 17.3R1. Supported on QFX5100, QFX5110, and QFX5200 switches starting with Junos OS Release 18.2R1. Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1. Supported on EX4600 switches starting with Junos OS Release 18.4R1. Periodic streaming is supported on on QFX10002 switches and PTX10002 routers starting with Junos OS Release 19.1R1. Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services. Supported on QFX5200 switches starting with Junos OS Release 19.2R1 for streaming telemetry information using gNMI services. Periodic streaming using gRPC services is supported on EX4300-MP switches starting with Junos OS Release 19.4R1, Periodic streaming using gRPC services is supported on EX2300, EX2300-MP, and EX3400 switches starting with Junos OS Release 20.2R1. You can also include the following to end of the resource path for CPU memory: `[name="mem-util-<memory-name>-size"]/value` `[name="mem-util-<memory-name>-bytes-allocated"]/value` `[name="mem-util-<memory-name>-utilization"]/value` `[name="mem-util-<memory-name>-< app-name>-allocations"]/value` `[name="mem-util-<memory-name>-< app-name>-frees"]/value` `[name="mem-util-<memory-name>-< app-name>-allocations-failed"]/value`
`/junos/system/linecard/npu/memory/`	Sensor for NPU Memory utilization statistics. Shown below, statistics are exported for the default FPC (FPC0). Multiples FPCs are supported. The component values and property values are names (like interface names). Starting in Junos OS Evolved Release 19.4R1, streaming statistics using gRPC and gNMI services on PTX10008 routers is supported. Starting in Junos OS Release 20.2R1, INITIAL_SYNC statistics using gNMI services on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches are supported. The following statistics are exported: `/components-memory/component[name='FPC0:NPU17']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-epp-mapid-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-epp-mapid-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-epp-mapid-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-l2domain-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-l2domain-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-l2domain-utilizationn']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash00-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash00-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash00-utilization']/` `:/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash10-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash10-allocatedd']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash10-utilization']/` `:/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-slu-my-mac-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-slu-my-mac-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-slu-my-mac-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-dlu-idb-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-dlu-idb-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-dlu-idb-utilization']/ }` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-final-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-final-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-final-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-remap-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-remap-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-remap-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-refbits-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-refbits-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-refbits-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-nh-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-nh-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-nh-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-mpls-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-mpls-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name=' mem-util-jnh-mpls-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-loadbal-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-loadbal-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-loadbal-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-egress-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-egress-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-egress-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jtree-memory-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jtree-memory-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jtree-memory-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-vfilter-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-vfilter-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-vfilter-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-phyfilter-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-phyfilter-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-phyfilter-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-action-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-action-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-action-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-tcam-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name=' mem-util-flt-tcam-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-tcam-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-0-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-0-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-0-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-1-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-1-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-1-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-2-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-2-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-2-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-3-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-3-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-3-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-4-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-4-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-4-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-scv-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-scv-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-scv-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-0-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-0-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-0-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-1-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-1-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-1-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-2-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-2-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-2-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-3-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-3-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-3-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-4-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-4-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-4-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-5-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-5-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-5-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-6-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-6-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-6-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-7-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-7-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-7-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name=' mem-util-flt-beta-1-bank-0-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-0-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-0-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-1-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-1-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-1-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-2-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-2-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-2-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-3-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-3-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-3-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-4-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-4-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-4-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-5-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-5-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-5-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-6-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-6-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-6-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-7-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-7-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-7-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-kht-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-kht-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-kht-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-bft-0-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-bft-0-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-bft-0-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-plt-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-plt-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-plt-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-kht-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-kht-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-kht-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-bft-0-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-bft-0-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-bft-0-utilization']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-plt-size']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-plt-allocated']/` `/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-plt-utilization']/`
`/junos/system/linecard/npu/utilization`	Sensor for NPU utilization on the Packet Forwarding Engine. Packet Forwarding Engine utilization is exported exported as a percentage using input notifications. The following packet statistics are also exported as part of this field: Loopback (pps) Recirculation (pps) WAN and host inject (pps) ASIC to host (pps) Shown below, statistics are exported for the default FPC (FPC0). Multiples FPCs are supported. The component values and property values are names (like interface names). Starting in Junos OS Evolved Release 19.4R1, streaming statistics using gRPC and gNMI services on PTX10008 routers is supported. The following statistics are exported: `/components-utilization/component[name='FPC0:NPU17'` `/components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-metric']` `/components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-Loopback-packet-rate']` `components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-Recirculation-packet-rate']` `/components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-Wan and Host inject-packet-rate']` `/components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-ASIC to host-packet-rate']`
`/junos/system/linecard/npu/utilization/`	Packet Forwarding Engine sensor for NPU processor utilization. Supported on MX Series routers with MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards starting with Junos OS Release 19.3R1 for streaing telemetry information using gRPC services. This feature provides a different level of exported statistics in comparison to previous releases because it uses the OpenConfig AFT model. Supported on MX2010 and MX2020 routers with MX2K-MPC11E line cards starting with Junos OS Release 20.1R1 for streaming telemetry information using gRPC services. Supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1 and later for INITIAL_SYNC statistics using gNMI services. You can also include the following to the end of the resource path for NPU utilization: `util-metric` `util-Disp 0 Pkts-packet-rate` `util-Disp 0 Pkts-average-instructions-per-packet` `util-Disp 0 Pkts-average-wait-cycles-per-packet` `util-Disp 0 Pkts-average-cycles-per-packet` `util-Disp 1 Pkts-packet-rate` `util-Disp 1 Pkts-average-instructions-per-packet` `util-Disp 1 Pkts-average-wait-cycles-per-packet` `util-Disp 1 Pkts-average-cycles-per-packet` `util-Disp 2 Pkts-packet-rate` `util-Disp 2 Pkts-average-instructions-per-packet` `util-Disp 2 Pkts-average-wait-cycles-per-packet` `util-Disp 2 Pkts-average-cycles-per-packet` `util-Disp 3 Pkts-packet-rate` `util-Disp 3 Pkts-average-instructions-per-packet` `util-Disp 3 Pkts-average-wait-cycles-per-packet` `util-Disp 3 Pkts-average-cycles-per-packet` `mem-util-EDMEM-average-util` `mem-util-EDMEM-highest-util` `mem-util-EDMEM-lowest-util` `mem-util-EDMEM-average-cache-hit-rate` `mem-util-EDMEM-highest-cache-hit-rate` `mem-util-EDMEM-lowest-cache-hit-rate` `mem-util-IDMEM-average-util` `mem-util-IDMEM-highest-util` `mem-util-IDMEM-lowest-util` `mem-util-IDMEM-average-cache-hit-rate` `mem-util-IDMEM-highest-cache-hit-rate` `mem-util-IDMEM-lowest-cache-hit-rate` `mem-util-Bulk DMEM-average-util` `mem-util-Bulk DMEM-highest-util` `mem-util-Bulk DMEM-lowest-util` `mem-util-Bulk DMEM-average-cache-hit-rate` `mem-util-Bulk DMEM-highest-cache-hit-rate` `mem-util-Bulk DMEM-lowest-cache-hit-rate`
`/junos/system/linecard/npu/utilization/`	Packet Forwarding Engine sensor for NPU processor utilization. Periodic streaming is supported on PTX10002 routers starting with Junos OS Release 19.1R1. Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers and PTX1000 and PTX10000 routers are supported on gRPC and gNMI services.
`/junos/system/linecard/interface/`	Packet Forwarding Engine sensor for physical interface traffic. Note: For PTX Series routers, for a specific interface, queue statistics are exported for each line card. For MX series routers, interface queue statistics are exported only from the slot on which an interface is configured. For Aggregated Ethernet interfaces, statistics are exported for the member physical interfaces. You must aggregate the counters at the destination server, or collector. If a physical interface is administratively down or operationally down, interface counters are not exported. Issuing an operational `clear` command, such as `clear interfaces statistics all`, does not reset statistics exported by the line card. Supported on PTX Series routers starting with Junos OS Release 15.1F3. Supported on MX Series routers starting with Junos OS Release 15.1F5. Supported on QFX10000 switches and PTX1000 routers starting with Junos OS Release 17.2R1. Supported on EX9200 switches and MX150 routers starting with Junos OS Release 17.3R1. Supported on QFX5100, QFX5110, and QFX5200 switches starting with Junos OS Release 18.2R1. Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1. Supported on EX4600 switches Starting with Junos OS Release 18.4R1. Periodic streaming is supported on QFX10002 switches and PTX10002 routers starting with Junos OS Release 19.1R1. Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches with Junos OS Release 19.2R1 on gRPC and gNMI services. Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft. Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported. Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1. Periodic streaming using gRPC services is supported on EX2300, EX2300-MP, and EX3400 switches starting with Junos OS Release 20.2R1. INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1. Streaming statistics using gRPC services or gNMI services is supported on PTX10008 routers starting with Junos OS Release 20.2R1.
`/junos/system/linecard/interface/logical/usage`	Packet Forwarding Engine sensor for logical interface statistics. Note: If a logical interface is operationally down, interface statistics continue to be exported. Issuing an operational `clear` command, such as `clear interfaces statistics all`, does not reset statistics exported by the line card. Note: If a logical interface is operationally down, interface statistics continue to be exported. Issuing an operational `clear` command, such as `clear interfaces statistics all`, does not reset statistics exported by the line card. Note: Locally injected packets from the Routing Engine are not exported. Note: Locally injected packets from the Routing Engine are not exported. Supported in Junos OS Release 15.1F5. Supported QFX10000 switches starting with on Junos OS Release 17.2R1. Supported on EX9200 switches and MX150 routers starting with Junos OS Release 17.3R1. Supported on QFX5100, QFX5110, and QFX5200 switches starting with Junos OS Release 18.2R1. Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1. Supported on EX4600 switches starting with Junos OS Release 18.4R1. Starting with Junos OS Release 19.1R1, periodic streaming is supported on QFX10002 switches and PTX10002 routers. Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches with Junos OS Release 19.2R1 on gRPC and gNMI services. Supported on QFX5200 switches starting with Junos OS Release 19.2R1 for streaming telemetry information using gNMI services. Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft. Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported. Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1. Periodic streaming using gRPC services is supported on EX3400 switches starting with Junos OS Release 20.2R1. INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1.
`/junos/system/linecard/interface/queue/`	Sensor for interface queue statistics. Starting with Junos OS Release 18.3R1, when a subscription is made to `/interfaces` on MX, EX, QFX, PTX, and ACX platforms, traffic and queue statistics are delivered in two separate sensors: /junos/system/linecard/interface/traffic/ /junos/system/linecard/interface/queue/ This can reduce the reap time for non-queue data for platforms supporting Virtual Output Queues (VOQ), such as PTX Series routers. Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services. Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft. Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1. INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1.
`/junos/system/linecard/interface/traffic/`	Sensor for interface traffic, exporting all fields except queue statistics. Starting with Junos OS Release 18.3R1, when a subscription is made to `/interfaces` on MX, EX, QFX, PTX, and ACX platforms, traffic and queue statistics are delivered in two separate sensors: /junos/system/linecard/interface/traffic/ /junos/system/linecard/interface/queue/ This can reduce the reap time for non-queue data for platforms supporting Virtual Output Queues (VOQ), such as PTX Series routers. Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services. Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft. Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1. INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1. Streaming statistics using gRPC services or gNMI services is supported on PTX10008 routers starting with Junos OS Release 20.2R1.
`/junos/system/linecard/intf-exp/`	Sensor for physical interface express statistics. Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.
`/junos/system/linecard/optical`	Sensor for optical alarms. Configure this sensor for `et-type-fpc/pic/port` (100-Gigabit Ethernet) interfaces. Supported on ACX6360 Universal Metro, MX Series, and PTX Series routers with a CFP2-DCO optics module starting with Junos OS Release 18.3R1. This module provides a high-density, long-haul OTN transport solution with MACSec capability. Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 19.2R1 on gRPC and gNMI services.
`/junos/system/linecard/otn`	Sensor for G.709 optical transport network (OTN) alarms. Configure this sensor on `ot-type-fpc/pic/port` interfaces. Supported on ACX6360 Universal Metro, MX Series, and PTX Series routers with a CFP2-DCO optics module starting with Junos OS Release 18.3R1. This module provides a high-density, long-haul OTN transport solution with MACSec capability. Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 19.2R1 on gRPC and gNMI services.
`/junos/system/linecard/qmon-sw/`	Sensor for congestion and latency monitoring statistics. Supported on QFX5100, QFX5110, and QFX5200 switches starting with Junos OS Release 18.2R1. Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1. Supported on EX4600 switches starting with Junos OS Release 18.4R1. Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 19.2R1 on gRPC and gNMI services. Supported on QFX5200 switches starting with Junos OS Release 19.2R1 for streaming telemetry information using gNMI services. Periodic streaming using gRPC services with EX4300-MP switches is supported starting with Junos OS Release 19.4R1. Periodic streaming using gRPC services is supported on EX3400 switches starting with Junos OS Release 20.2R1. INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1.
`/junos/system/linecard/services/inline-jflow`	Sensor for inline active flow monitoring services statistics. Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 19.2R1 on gRPC and gNMI services. When configuring inline active flow monitoring in Junos, you can apply version 9 or IPFIX flow templates to define a flow record template suitable for IPv4 or IPv6 MPLS and bridging traffic. For more information, see Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9 Flow Templates. Supported on MX Series operating with MPC10E-15C-MRATE line-rate cards starting with Junos OS Release 19.2R1. Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft. Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1. Periodic streaming using gRPC services on PTX10008 routers is supported starting with Junos OS Evolved Release 20.1R1.
`/local-routes/static-routes/static/` `/local-routes/local-aggregates/aggregate/`	Sensor for local routing. These sensors support OpenConfig version 1.0.0 data model openconfig-local-routing.yang. Starting in Junos OS Release 20.2R1, EX2300, EX3400, EX4300, EX4600, and EX9200 switches support streaming statistics with gRPC services. You can add the following end paths for static routes: `prefix` `state/prefix` `state/set-tag` `next-hops/next-hop/index` `next-hops/next-hop/state/index` `next-hops/next-hop/state/next-hop` `next-hops/next-hop/state/metric` You can add the following end paths for aggregate routes: `prefix` `state/prefix` `state/discard` `state/set-tag`
`/network-instances/network-instance/protocols/protocol/bgp/global/`	Sensor for BGP global statistics. This sensors support OpenConfig version 4.0.1 data model openconfig-bgp-neighbor.yang and openconfig-bgp-policy.yang. Starting in Junos OS Release 20.2R1, EX2300, EX3400, EX4300, EX4600, and EX9200 switches support streaming statistics with gRPC services. You can add the following end paths: `config/as` `config/router-id` `confederation/config/identifier` `confederation/config/member/as` `graceful-restart/config/enabled` `graceful-restart/config/restart-time` `graceful-restart/config/stale-routes-time` `graceful-restart/config/helper-only` `route-selection-options/config/always-compare-med` `route-selection-options/config/ignore-as-path-length` `route-selection-options/config/external-compare-router-id` `route-selection-options/config/advertise-inactive-routes` `route-selection-options/config/enable-aigp` `route-selection-options/config/ignore-next-hop-igp-metric` `afi-safis/afi-safi/config/afi-safi-name` `afi-safis/afi-safi/config/enabled` `afi-safis/afi-safi/graceful-restart/config/enabled` `afi-safis/afi-safi/route-selection-options/config/enable-aigp` `afi-safis/afi-safi/add-paths/config/receive` `afi-safis/afi-safi/add-paths/config/send` `afi-safis/afi-safi/add-paths/config/send-max` `afi-safis/afi-safi/add-paths/config/eligible-prefix-policy` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/shutdown-threshold-pct` `ipv6-unicast/prefix-limit/config/restart-timer` `ipv4-labeled-unicast/prefix-limit/config/max-prefixes` `ipv4-labeled-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safi/ipv6-labeled-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/max-prefixes` `afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/prevent-teardown` `afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/prevent-teardown` `afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/prevent-teardown` `afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/prevent-teardown` `afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l2vpn-evpn/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l2vpn-evpn/prefix-limit/config/prevent-teardowns` `afi-safis/afi-safi/l2vpn-evpn/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l2vpn-evpn/prefix-limit/config/restart-time`
`/network-instances/network-instance/protocols/neighbor/neighbors/`	Sensor for BGP peer statistics. This sensors support OpenConfig version 4.0.1 data model openconfig-bgp-neighbor.yang and openconfig-bgp-policy.yang. Starting in Junos OS Release 20.2R1, EX2300, EX3400, EX4300, EX4600, and EX9200 switches support streaming statistics with gRPC services. You can add the following end paths: `config/peer-group` `config/neighbor-address` `config/enabled` `config/peer-as` `config/local-as` `config/peer-type` `config/auth-password` `config/remove-private-as` `config/route-flap-damping` `config/description` `timers/config/connect-retry` `timers/config/hold-time` `timers/config/minimum-advertisement-interval` `transport/config/tcp-mss` `transport/config/mtu-discovery` `transport/config/passive-mode` `transport/config/local-address` `error-handling/config/treat-as-withdraw` `graceful-restart/config/enabled` `graceful-restart/config/restart-time` `graceful-restart/config/stale-routes-time` `graceful-restart/config/helper-only` `logging-options/config/log-neighbor-state-changes` `ebgp-multihop/config/enabled` `ebgp-multihop/config/multihop-ttl` `route-reflector/config/route-reflector-cluster-id` `route-reflector/config/route-reflector-client` `as-path-options/config/allow-own-as` `as-path-options/config/replace-peer-as` `as-path-options/config/disable-peer-as-filter` `use-multiple-paths/config/enabled` `use-multiple-paths/ebgp/config/allow-multiple-as` `apply-policy/config/import-policy` `apply-policy/config/export-policy` `afi-safis/afi-safi/config/afi-safi-name` `afi-safis/afi-safi/config/enabled` `afi-safis/afi-safi/graceful-restart/config/enabled` `afi-safis/afi-safi/add-paths/config/receive` `afi-safis/afi-safi/add-paths/config/send` `afi-safis/afi-safi/add-paths/config/send-max` `afi-safis/afi-safi/add-paths/config/eligible-prefix-policy` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/retart-timer`
`/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/`	Sensor for BGP peer group statistics. This sensors support OpenConfig version 4.0.1 data model openconfig-bgp-neighbor.yang and openconfig-bgp-policy.yang. Starting in Junos OS Release 20.2R1, EX2300, EX3400, EX4300, EX4600, and EX9200 switches support streaming statistics with gRPC services. You can add the following end paths: `config/peer-group-name` `config/peer-as` `config/local-as` `config/peer-type` `config/auth-password` `config/remove-private-as` `route-flap-damping` `description` `config/connect-retry` `config/hold-time` `config/minimum-advertisement-interval` `config/tcp-mss` `config/mtu-discovery` `config/passive-mode` `config/local-address` `error-handling/config/treat-as-withdraw` `graceful-restart/config/enabled` `graceful-restart/config/restart-time` `graceful-restart/config/stale-routes-time` `graceful-restart/config/helper-only` `logging-options/config/log-neighbor-state-changes` `ebgp-multihop/config/enabled` `ebgp-multihop/config/multihop-ttl` `route-reflector/config/route-reflector-cluster-id` `route-reflector/config/route-reflector-client` `as-path-options/config/allow-own-as` `as-path-options/config/replace-peer-as` `use-multiple-paths/config/enabled` `use-multiple-paths/ebgp/config/allow-multiple-as` `use-multiple-paths/ebgp/config/maximum-paths` `use-multiple-paths/ibgp/config/maximum-paths` `apply-policy/config/import-policy` `apply-policy/config/export-policy` `afi-safis/afi-safi/config/afi-safi-name` `afi-safis/afi-safi/config/enabled` `afi-safis/afi-safi/graceful-restart/config/enabled` `afi-safis/afi-safi/add-paths/config/receive` `afi-safis/afi-safi/add-paths/config/send` `afi-safis/afi-safi/add-paths/config/send-max` `afi-safis/afi-safi/add-paths/config/eligible-prefix-policy` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv4-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/prevent-teardown` `/afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv6-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv4-labeled-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/ipv6-labeled-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l3vpn-ipv4-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l3vpn-ipv6-unicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l3vpn-ipv4-multicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l3vpn-ipv6-multicast/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l2vpn-vpls/prefix-limit/config/restart-timer` `afi-safis/afi-safi/l2vpn-evpn/prefix-limit/config/max-prefixes` `afi-safis/afi-safi/l2vpn-evpn/prefix-limit/config/prevent-teardown` `afi-safis/afi-safi/l2vpn-evpn/prefix-limit/config/shutdown-threshold-pct` `afi-safis/afi-safi/l2vpn-evpn/prefix-limit/config/restart-timer`
`/network-instances/network-instance/protocols/protocol/bgp/`	Sensor for BGP peer information. Periodic streaming using gRPC services on PTX10003 routers is supported, starting with Junos OS Evolved Release 19.2R1. Periodic streaming using gRPC services is supported on any platform family that supports containerized routing protocol process (cRPD) starting with Junos OS Release 20.2R1. cRPD is Juniper’s routing protocol process (rpd) decoupled from Junos OS and packaged as a Docker container to run in Linux-based environments. You can also add the following end paths: `neighbors/neighbor/afi-safis/afi-safi/state/active` `neighbors/neighbor/afi-safis/afi-safi/state/prefixes/installed` `neighbors/neighbor/afi-safis/afi-safi/state/prefixes/received` `neighbors/neighbor/afi-safis/afi-safi/state/prefixes/sent` `neighbors/neighbor/afi-safis/afi-safi/state/prefixes/rejected` `neighbors/neighbor/state/admin-state` `neighbors/neighbor/state/established-transitions` `neighbors/neighbor/state/last-established` `neighbors/neighbor/state/messages/received/notification` `neighbors/neighbor/state/messages/received/update` `neighbors/neighbor/state/messages/sent/notification` `neighbors/neighbor/state/messages/sent/update` `neighbors/neighbor/state/session-state` `neighbors/neighbor/state/supported-capabilities` `transport/state/local-address` `transport/state/remote-address` `transport/state/remote-port`
`/network-instances/network-instance/protocols/protocol/bgp/`	Sensor for BGP peer information. Supported on QFX5200 switches for streaming and ON_CHANGE statistics export through gNMI services starting with Junos OS Release 19.2R1. You can also add the following end paths: `global/afi-safis/afi-safi/state/total-prefixes` `neighbors/neighbor/state/session-state` `neighbors/neighbor/state/messages/sent/UPDATE` `neighbors/neighbor/state/messages/received/UPDATE` `neighbors/neighbor/transport/state/local-address` `neighbors/neighbor/state/peer-as` `neighbors/neighbor/afi-safis/afi-safi/ipv4-unicast/prefix-limit/state/max-prefixes` `neighbors/neighbor/` `neighbors/neighbor/` `neighbors/neighbor/state/session-admin-status` `neighbors/neighbor/state/session-status` `neighbors/neighbor/state/established-transitions` `neighbors/neighbor/state/interface-error` `neighbors/neighbor/afi-safis/afi-safi/state/prefix-limit-exceeded`
`/network-instances/network-instance/protocols/protocol/bgp/` Note: Starting with Junos OS Release 17.4R1 on MX Series and PTX Series routers, you can provision Junos Telemetry Interface sensors to export data for BGP routing tables (RIBs) for IPv4 and IPv6 routes. For BGP routing table paths, the `/network-instances/network-instance/` path is not supported. Each address family supports exporting data for five different tables, a main routing table, and four per-neighbor tables: local-rib— main BGP routing table for the main routing instance. adj-rib-in-pre— NLRI updates received from the neighbor before any local input policy filters have been applied. adj-rib-in-post— routes received from the neighbor eligible for best-path selection after local input policy filters have been applied. adj-rib-out-pre— routes eligible for advertising to the neighbor before output policy filters have been applied. adj-rib-out-post— routes eligible for advertising to the neighbor after output policy filters have been applied. Use the following paths to export data for each BGP routing table. You can specify to export data either for IPv4 or IPv6 for each table: `/bgp-rib/afi-safis/afi-safi/ipv4-unicast/loc-rib/` `/bgp-rib/afi-safis/afi-safi/ipv6-unicast/loc-rib/` `/bgp-rib/afi-safis/afi-safi/ipv4-unicast/ neighbors/neighbor/adj-rib-in-pre/` `/bgp-rib/afi-safis/afi-safi/ipv6-unicast/ neighbors/neighbor/adj-rib-in-pre/` `/bgp-rib/afi-safis/afi-safi/ipv4-unicast/ neighbors/neighbor/adj-rib-in-post/` `/bgp-rib/afi-safis/afi-safi/ipv6-unicast/ neighbors/neighbor/adj-rib-in-post/` `/bgp-rib/afi-safis/afi-safi/ipv4-unicast/ neighbors/neighbor/adj-rib-out-pre/` `/bgp-rib/afi-safis/afi-safi/ipv6-unicast/ neighbors/neighbor/adj-rib-out-pre/` `/bgp-rib/afi-safis/afi-safi/ipv4-unicast/ neighbors/neighbor/adj-rib-out-post/` `/bgp-rib/afi-safis/afi-safi/ipv6-unicast/ neighbors/neighbor/adj-rib-out-post/`	Sensor for BGP peer information. Supported on QFX10000 switches and QFX5200 switches starting with Junos OS Release 17.2R1. Supported on PTX1000 routers, EX4600 and EX9200 switches, and QFX5110 switches starting with Junos OS Release 17.3R1. Starting with Junos OS Release 18.1R1, QFX5100 switches are also supported. Starting with Junos OS Release 18.3R1, QFX5120-48Y and EX4650 switches are also supported. Starting with Junos OS Release 19.1R1, periodic streaming on QFX10002 switches and PTX10002 routers is supported. Starting with Junos OS Release 19.2R1, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800 and vSRX are also supported. Starting with Junos OS Release 20.2R1, periodic streaming using gRPC services is supported on EX3400 switches. Starting with Junos OS Release 20.2R1, streaming pseudo interface statistics through Routing Engine sensors is supported using gRPC services or gNMI services with SRX5400, SRX5600, and SRX5800 Service Gateways. Previously, streaming statistics was only supported through gRPC services. Note: Starting with Junos OS Release 17.3R1, telemetry data streamed through gRPC for BGP peers is reported separately for each configured routing instance. If your Juniper Network device is running Junos OS Release 17.3R1 or later, you must prepend the following to the beginning of any path you specify to stream statistics for BGP, with the exception of paths for routing tables: `/network-instances/network-instance[name_'instance-name']/ protocols/protocol/` Starting with Junos OS Release 17.3R1, the following paths are also supported: `/network-instances/network-instance/protocols/protocol/ bgp/neighbors/neighbor/afi-safis/afi-safi/state/prefixes/accepted` `/network-instances/network-instance/protocols/protocol/ bgp/neighbors/neighbor/afi-safis/afi-safi/state/prefixes/rejected` `/network-instances/network-instance/protocols/protocol/ bgp/neighbors/neighbor/afi-safis/afi-safi/state/active` `/network-instances/network-instance/protocols/protocol/ bgp/neighbors/neighbor/afi-safis/afi-safi/state/queues/output` `/network-instances/network-instance/protocols/protocol/ bgp/neighbors/neighbor/afi-safis/afi-safi/state/queues/input` `/network-instances/network-instance/protocols/protocol/ bgp/neighbors/snmp-peer-index` `/network-instances/network-instance/protocols/protocol/ bgp/neighbors/neighbor/state/ImportEval` `/network-instances/network-instance/protocols/protocol/ bgp/neighbors/neighbor/state/ImportEvalPending` `/network-instances/network-instance/protocols/protocol/ bgp/neighbors/neighbor/state/messages/received/notification` `/network-instances/network-instance/protocols/protocol/ bgp/neighbors/neighbor/state/messages/sent/notification` `/network-instances/network-instance/protocols/protocol/ bgp/transport/state/remote-port` `/network-instances/network-instance/protocols/protocol/ bgp/neighbors/neighbor/state/supported-capabilities` Note: For all the following paths, with the exception of paths for routing tables, if your Juniper Networks device is running Junos OS Release 17.3R1 or later, you must prepend the following in front of the path: `/network-instances/network-instance[name_'instance-name']/protocols/protocol/` You can also include the following at the end path to `/network-instances/network-instance[name_'instance-name']/protocols/protocol/ bgp/neighbors/neighbor/`: `state/session-state` `state/messages/sent/update` `state/messages/received/update` `transport/state/local-address` `transport/state/remote-address` `state/peer-as` `afi-safis/afi-safi/state/prefix-limit/state/max-prefixes` `afi-safis/afi-safi/state/active` `state/session-status` `state/session-admin-status` `state/session-established-transitions` `state/interface-error` `state/prefix-limited-exceeded` `state/last-established` `established-transitions` You can also include the following at the end path to `/network-instances/network-instance[name_'instance-name']/protocols/protocol/ /bgp/global/`: `afi-safis/afi-safi/state/total-prefixes` You can also include the following at the end path to `/network-instances/network-instance[name_'instance-name']/protocols/protocol/ /bgp/peer-groups/peer-group[name_'peer-group-name]/`: `afi-safis/afi-safi/add-paths/eligible-prefix-policy` `state/peer-count/` Note: For paths that export data for BGP routing tables, which are supported starting with Junos OS Release 17.4R1, you can apend the following to each of the paths: `/num-routes` `/routes/route/prefix` `/routes/route/attributes` `/routes/route/attributes/origin` `/routes/route/attributes/as-path` `/routes/route/attributes/next-hop` `/routes/route/attributes/med` `/routes/route/attributes/local-pref` `/routes/route/attributes/atomic-aggr` `/routes/route/attributes/aggregator/as` `/routes/route/attributes/aggregator/as4` `/routes/route/attributes/aggregator/address` `/routes/route/ext-attributes/` `/routes/route/ext-attributes/community` `/routes/route/ext-attributes/originator-id` `/routes/route/ext-attributes/cluster-list` `/routes/route/ext-attributes/extended-community` `/routes/route/ext-attributes/aigp` `/routes/route/ext-attributes/path-id` `/routes/route/ext-attributes/unknown-attribute` `/routes/route/ext-attributes/unknown-attribute/attr-type` `/routes/route/ext-attributes/unknown-attribute/attr-len` `/routes/route/ext-attributes/unknown-attribute/attr-value` `/routes/route/last-modified-date` `/routes/route/last-update-received` `/routes/route/valid-route` `/routes/route/invalid-reason` `/routes/route/best-path`
/network-instances/network-instance/protocols/protocol/bgp	Sensor for BGP peer information. ON_CHANGE BGP peer statistics export using gRPC services and gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000, PTX10000 routers and QFX5100 and QFX5200 switches, starting with Junos OS Release 20.2R1. `neighbors/neighbor/afi-safis/afi-safi/ state/active` (ON_CHANGE) `neighbors/neighbor/afi-safis/afi-safi/ state/prefixes` (ON_CHANGE) `neighbors/neighbor/afi-safis/afi-safi/ state/prefixes/received` (ON_CHANGE) `neighbors/neighbor/afi-safis/afi-safi/ state/prefixes/sent` (ON_CHANGE) `neighbors/neighbor/afi-safis/afi-safi/ state/prefixes/rejected` (ON_CHANGE) `neighbors/neighbor/state/admin-state` (ON_CHANGE) `neighbors/neighbor/state/ established-transitions` (ON_CHANGE) `neighbors/neighbor/state/last-established` (ON_CHANGE) `neighbors/neighbor/state/messages/ received/notification` (stream only) `neighbors/neighbor/messages/received/ update` (stream only) `neighbors/neighbor/state/messages/ sent/notification` (stream only) `neighbors/neighbor/state/messages/ sent/update` (stream only) `neighbors/neighbor/state/session-state` (ON_CHANGE) `neighbors/neighbor/state/supported-capabilities` (ON_CHANGE) `transport/state/local-address` (ON_CHANGE) `transport/state/remote-address` (ON_CHANGE) `transport/state/remote-port` (ON_CHANGE)
`/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/`	Sensor for instance level statistics. Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/peer/`	Route statistics per peer sensor. Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/ethernet-segment/`	Ethernet segment information sensor). Statistics include EVPN designated forwarder ON_CHANGE leafs esi and designated-forwarder. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/interfaces/`	Local interface information sensor.) Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/irb-interfaces/`	Local integrated routing and bridging (IRB) interface information sensor. Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/sg-db/`	EVPN IGMP snooping database (type 6) sensor. Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/sg-db/sgdb-esi`	EVPN IGMP join sync (type 7) ad leave sync (type 8) sensor. Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/assisted-replication/`	Sensor to relate selected replicator on AR leaf. Use the Telemetry Explorer tool to see leaves for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, and QFX5200 switches.
`/network-instances/network-instance[instance-name='name']//protocols/protocol/evpn/ethernet-segment`	EVPN ON_CHANGE notifications sensor. Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, and QFX5200 switches.
`/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/vxlan-tunnel-end-point/`	Overlay VX-LAN tunnel information sensor. This sensor also delivers VTEP information ON_CHANGE leafs: `source_ip_address` `remote_ip_address` `status` `mode` `nexthop-index` `event-type` `source-interface` Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[instance-name='name']/mac_db/entries/entry/`	EVPN MAC table information sensor. Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[instance-name='name']/macip_db/entries/entry/`	MAC-IP or ARP-ND table sensor. Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[name='name']/macip-table-info/`	MAC-IP ON_CHANGE table information sensor. Statistics include leafs: `status` `learning` `aging-time` `table-sixe` `proxy-macip` `num-local-entries` Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[name='name']/macip-table/entries/entry/`	MAC-IP ON_CHANGE entry information sensor. Statistics include leafs: `ip-address` `mac-address` `vlan-id` `vni` Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance[instance-name='name']/bd/`	Bridge domain or VLAN information sensor. Use the Telemetry Explorer tool to see leafs for this resource path. Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.
`/network-instances/network-instance/protocols/protocol/isis/levels/level/`	Sensor for IS-IS routing protocol statistics. Statistics are exported separately for each routing instance. To specify a routing-instance name: /`network-instances/network-instance[name_'instance-name']/protocols/protocol/isis/levels/level/` `/network-instances/network-instance[name_'instance-name']/protocols/protocol/isis/interfaces/interface/levels/level/` Starting with Junos OS Release 20.1R1, streaming statistics is supported with gRPC and gNMI services, and where indicated, ON_CHANGE statistics, for MX960, PTX1000, and PTX10000 routers. The following paths are also supported: `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/lsp-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/maximum-area-addresses` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/version` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/version2` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/id-length` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/pdu-type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/remaining-lifetime` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/lsp-install-time` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/sequence-number` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/checksum` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/pdu-length` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/is-type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/state/flag/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/tlv-type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/state/tlv-type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/area-address/state/address` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/nlpid/state/nlpid` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv4-interface-addresses/state/address` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-interface-addresses/state/address` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv4-te-router-id/state/te-router-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/lsp-buffer-size/state/size` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/hostname/state/hname` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/system-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/state/metric` `/network-instances/network-instance/protocols/protocol/isis/instances/instance/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/state/system-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/state/type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/admin-group/state/admin-group` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/link-id/state/local` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/link-id/state/remote` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/ipv4-interface-address/state/address` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/ipv4-neighbor-address/state/address` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/te-default-metric/state/metric` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/max-link-bandwidth/state/bandwidth` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/max-reservable-link-bandwidth/state/bandwidth` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/unreserved-bandwidth/setup-priority/priority` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/unreserved-bandwidth/setup-priority/priority` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/unreserved-bandwidth/setup-priority/state/priority` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/unreserved-bandwidth/setup-priority/state/bandwidth` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/bandwidth-constraints/bandwidth-constraint/model-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/bandwidth-constraints/bandwidth-constraint/state/model-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/bandwidth-constraints/bandwidth-constraint/constraints/constraint/constraint-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/bandwidth-constraints/bandwidth-constraint/constraints/constraint/state/constraint-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/bandwidth-constraints/bandwidth-constraint/constraints/constraint/state/bandwidth` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/adjacency-sids/adj-sid/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/adjacency-sids/adj-sid/state/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/adjacency-sids/adj-sid/state/flags` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/adjacency-sids/adj-sid/state/weight` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/adjacency-sids/adj-sid/state/weight` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/lan-adjacency-sids/lan-adj-sid/state/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/lan-adjacency-sids/lan-adj-sid/state/flags` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/lan-adjacency-sids/lan-adj-sid/state/weight` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/subtlvs/subtlv/lan-adjacency-sids/lan-adj-sid/state/neighbor-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/undefined-subtlvs/undefined-subtlv/type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/undefined-subtlvs/undefined-subtlv/state/type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/undefined-subtlvs/undefined-subtlv/state/length` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-is-reachability/neighbors/neighbor/undefined-subtlvs/undefined-subtlv/state/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv4-srlgs/ipv4-srlg/instance-number` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv4-srlgs/ipv4-srlg/state/instance-number` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv4-srlgs/ipv4-srlg/state/system-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv4-srlgs/ipv4-srlg/state/psn-number` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv4-srlgs/ipv4-srlg/state/flags` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv4-srlgs/ipv4-srlg/state/ipv4-interface-address` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv4-srlgs/ipv4-srlg/state/ipv4-neighbor-address` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv4-srlgs/ipv4-srlg/state/srlg-value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/prefix` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/state/prefix` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/state/up-down` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/state/s-bit` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/state/metric` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/tag/state/tag32` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sids/prefix-sid/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sids/prefix-sid/state/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sids/prefix-sid/state/flags` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sids/prefix-sid/state/algorithm` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/length` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/prefix` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/state/prefix` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/state/up-down` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/state/s-bit` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/state/x-bit` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/state/metric` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/tag/state/tag32` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sids/prefix-sid/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sids/prefix-sid/state/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sids/prefix-sid/state/flags` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sids/prefix-sid/state/algorithm` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/pv6-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/length` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/router-capability/subtlvs/subtlv/segment-routing-capability/state/flags` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/router-capability/subtlvs/subtlv/segment-routing-capability/srgb-descriptors/srgb-descriptor/range` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/router-capability/subtlvs/subtlv/segment-routing-capability/srgb-descriptors/srgb-descriptor/state/label` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/router-capability/subtlvs/subtlv/segment-routing-capability/srgb-descriptors/srgb-descriptor/state/range`
`/network-instances/network-instance/protocols/protocol/isis/instances/instance`	Sensor for IS-IS routing protocol statistics. Statistics are exported separately for each routing instance. To specify a routing-instance name: `/network-instances/network-instance[name_'instance-name']/protocols/protocol/isis/interfaces/interface/levels/level/` Starting with Junos OS Release 20.1R1, streaming statistics is supported with gRPC and gNMI services, and where indicated, ON_CHANGE statistics, for MX960, PTX1000, and PTX10000 routers. The following endpoints are also supported: `/network-instances/network-instance/protocols/protocol/isis/instances/instance/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/capability/instance-number` `/network-instances/network-instance/protocols/protocol/isis/instances/instance/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/capability/state/instance-number` `/network-instances/network-instance/protocols/protocol/isis/instances/instance/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/capability/state/flags` `/network-instances/network-instance/protocols/protocol/isis/instances/instance/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/capability/state/router-id` `/network-instances/network-instance/protocols/protocol/isis/instances/instance/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/capability/subtlvs/subtlv/type` `/network-instances/network-instance/protocols/protocol/isis/instances/instance/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/capability/subtlvs/subtlv/state/type` `/network-instances/network-instance/protocols/protocol/isis/instances/instance/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/capability/subtlvs/subtlv/segment-routing-algorithms/state/algorithm`
`/network-instances/network-instance/protocols/protocol/isis/interfaces/interface`	Sensor for IS-IS routing protocol interface statistics. Statistics are exported separately for each routing instance. To specify a routing-instance name: `/network-instances/network-instance[name_'instance-name']/protocols/protocol/isis/interfaces/interface/levels/level/` Periodic streaming using gRPC and gNMI services is supported with on MX960, PTX1000, and PTX10000 routers starting with Junos OS Release 20.1R1. ON_CHANGE statistics are also supported, where indicated. Periodic streaming using gRPC services is supported on EX2300, EX2300-MP, and EX3400 switches starting with Junos OS Release 20.2R1. The following end points are also supported: `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/system-id` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/neighbor-snpa` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/dis-system-id` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/neighbor-circuit-type` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/local-extended-circuit-id` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/neighbor-extended-circuit-id` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/nlpid` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/area-address` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/adjacency-type` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/adjacency-state` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/lan-adjacency-state` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/multi-topo` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/restart-support` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/restart-suppress` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/restart-status` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/ipv4-neighbor-address` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/ipv6-neighbor-address`
`/junos/task-memory-information/`	Sensor for memory utilization for routing protocol task. Supported on QFX10000 switches and QFX5200 switches starting with Junos OS Release 17.2R1. Supported on PTX1000 routers, EX4600 and EX9200 switches and QFX5110 switches starting with Junos OS Release 17.3R1. Starting with Junos OS Release 18.1R1, QFX5100 switches are also supported. Starting with Junos OS Release 18.3R1, QFX5120-48Y and EX4650 switches are also supported. Starting with Junos OS Release 19.1R1, periodic streaming is supported on QFX10002 switches and PTX10002 routers. Starting with Junos OS Release 19.2R1, periodic streaming using gRPC services on SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800 and vSRX Service Gateways is supported. Starting with Junos OS Release 19.2R1, streaming and ON_CHANGE statistics export using gNMI services is supported on QFX5200 switches. Starting with Junos OS Release 20.2R1, streaming pseudo interface statistics through Routing Engine sensors is supported using gRPC services or gNMI services with SRX5400, SRX5600, and SRX5800 Service Gateways. Previously, streaming statistics was only supported through gRPC services. You can also include the following at the end path to `/junos/task-memory-information/`: `task-memory-overall-report/task-size-block-list/task-size-block/tsb-size` `task-memory-overall-report/task-size-block-list/task-size-block/tsb-alloc-bytes` `task-memory-overall-report/task-size-block-list/task-size-block/tsb-allocs` `task-memory-overall-report/task-size-block-list/task-size-block/tsb-max-allocs` `task-memory-overall-report/task-size-block-list/task-size-block/tsb-max-bytes` `task-memory-overall-report/task-size-block-list/task-size-block/tsb-free-bytes` `task-memory-overall-report/task-memory-total-bytes` `task-memory-overall-report/task-memory-total-max-bytes` `task-memory-information/task-memory-overall-report/task-memory-total-free-bytes` `task-memory-allocator-report/task-block-list/task-block/tb-name` `task-memory-allocator-report/task-block-list/task-block/tb-size` `task-memory-allocator-report/task-block-list/task-block/tb-alloc-size` `task-memory-allocator-report/task-block-list/task-block/tb-alloc-blocks` `task-memory-allocator-report/task-block-list/task-block/tb-alloc-bytes` `task-memory-allocator-report/task-block-list/task-block/tb-max-alloc-blocks` `task-memory-allocator-report/task-lite-page-list/task-lite-page/tlp-name` `task-memory-allocator-report/task-lite-page-list/task-lite-page/tlp-alloc-bytes` `task-memory-allocator-report/task-memory-total-bytes` `task-memory-information/task-memory-allocator-report/task-memory-total-max-bytes` `task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-name` `task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-allocs` `task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-alloc-bytes` `task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-max-allocs` `task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-max-alloc-bytes` `task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-function-calls` `task-memory-malloc-usage-report/task-memory-total-bytes` `task-memory-malloc-usage-report/task-memory-total-max-bytes` `task-memory-max-dynamic-allocs` `task-memory-bss-bytes` `task-memory-max-bss-bytes` `task-memory-page-data-bytes` `task-memory-max-page-data-bytes` `task-memory-dir-bytes` `task-memory-max-dir-bytes` `task-memory-total-bytes-in-use` `task-memory-total-bytes-percent`
`/junos/system/linecard/firewall/`	Sensor for firewall filter counters and policer counters. Each line card reports counters separately. Supported on QFX10000 switches starting with Junos OS Release 17.2R1. Supported on PTX1000 routers and EX9200 switches starting with Junos OS Release 17.3R1. Supported on QFX5100, QFX5110, and QFX5200 switches starting with Junos OS Release 18.2R1. Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1. Supported on EX4600 switches starting with Junos OS Release 18.4R1. Starting with Junos OS Release 19.1R1, periodic streaming is supported on QFX10002 switches and PTX10002 routers. Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers are supported. Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services. Supported on QFX5200 switches starting with Junos OS Release 19.2R1 for streaming telemetry information using gNMI services. Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft. Periodic streaming using gRPC services with EX4300-MP switches is supported starting with Junos OS Release 19.4R1. Periodic streaming using gNMI services with PTX10003 routers is supported starting with Junos OS Evolved Release 19.4R1. Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1. Periodic streaming using gRPC services is supported on EX2300, EX2300-MP, and EX3400 switches starting with Junos OS Release 20.2R1. INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1. Note: Hierarchical policer statistics are collected for MX Series routers only. Traffic-class counter statistics are collected for PTX Series routers and QFX10000 switches only. Firewall counters are exported even if the interface to which the firewall filter is attached is operationally down. The following OpenConfig paths are supported: `junos/firewall/firewall-stats/[name='filter-name']/timestamp` `/junos/firewall/firewall-stats/[name='filter-name']/ memory-usage/[name='memory-type']/allocated` `/junos/firewall/firewall-stats/[name='filter-name']/ counter-stats/[name='counter-name']/packets` `/junos/firewall/firewall-stats/[name='filter-name']/ counter-stats/[name='couner-name']/bytes` `/junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/out-of-spec-packets` `/junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/out-of-spec-bytes` `/junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/offered-packets` `/junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/offered-bytes` `/junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/transmitted-packets` `/junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/transmitted-bytes` `/junos/firewall/firewall-stats/[name='filter-name']/ hierarchical-policer-stats/[name='hierarchical-policer-name']/premium-packets` (MX Series only) `/junos/firewall/firewall-stats/[name='filter-name']/ hierarchical-policer-stats/[name='hierarchical-policer-name']/premium-bytes` (MX Series only) `/junos/firewall/firewall-stats/[name='filter-name']/ hierarchical-policer-stats/[name='hierarchical-policer-name']/aggregate-packets` (MX Series only) `/junos/firewall/firewall-stats/[name='filter-name']/ hierarchical-policer-stats/[name='hierarchical-policer-name']/aggregate-bytes` (MX Series only)
`/junos/system/linecard/intf-exp/`	Interface express sensor. This sensor leverages statistics out of the physical interface sensor, providing faster and more frequent operational status statistics. Only the physical interfaces’ operational status from the Flexible PIC Concentrator (FPC) is collected and reported. Statistics from the Routing Engine interface are not reported. Supported on PTX1000, PTX3000, PTX5000, and PTX10000 starting with Junos OS Release 18.1R1. Supported on MX960, MX2010, and MX2020 routers starting with Junos OS Release 19.3R1.
`/interfaces/interface/`	Sensor for physical interface traffic. Note: For PTX Series routers, for a specific interface, queue statistics are exported for each line card. For MX series routers, interface queue statistics are exported only from slot on which an interface is configured. For Aggregated Ethernet interfaces, statistics are exported for the member physical interfaces. You must aggregate the counters at the destination server, or collector. If a physical interface is administratively down or operationally down, interface counters are not exported. Only fields with a non-zero value are exported. Supported on QFX10000 switches and PTX1000 routers starting with Junos OS Release 17.2R1. Supported on EX9200 switches and MX150 routers starting with Junos OS Release 17.3R1. Starting with Junos OS Release 18.1R1, QFX5100 switches are also supported. Starting with Junos OS Release 18.3R1, QFX5120-48Y and EX4650 switches are also supported. Starting with Junos OS Release 18.4R1, EX4600 switches are also supported. Starting with Junos OS Release 19.1R1, periodic streaming is supported on QFX10002 switches and PTX10002 routers. Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers are supported. Starting with Junos OS Release 19.2R1, QFX5200 supports streaming telemetry information using gNMI services. Support on PTX10003 routers starting in Junos OS Evolved Release 19.1R1. Starting with Junos OS Release 19.2R1, periodic streaming using gNMI services is supported on QFX5100, QFX5110, QFX5120, QFX5200 and QFX5210 switches. Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gRPC services with PTX10008 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported. Starting with Junos OS Release 20.1R1, ON_CHANGE statistics using gNMI services with MX960, MX2020, PTX1000, and PTX5000 routers. These routers support OpenConfig model: openconfig-interfaces.yang: oc-ext:openconfig-version 2.4.1 Starting with Junos OS Release 20.2R1, streaming revenue interface statistics through Packet Forwarding Engine sensors and pseudo interface statistics through Routing Engine sensors is supported using gRPC services or gNMI services with SRX5400, SRX5600, and SRX5800 Service Gateways. Starting with Junos OS Release 18.3R1, when a subscription is made to `/interfaces` on MX, EX, QFX, PTX, and ACX platforms, traffic and queue statistics are delivered in two separate sensors. This can reduce the reap time for non-queue data for platforms supporting Virtual Output Queues (VOQ), such as PTX Series routers. The two sensors are: /junos/system/linecard/interface/traffic/ exports all fields except queue statistics. /junos/system/linecard/interface/queue/ exports queue statistics. Note: End paths supporting ON_CHANGE streaming are indicated. The following paths are also supported: `/interfaces/interface[name='interface-name']/state/parent_ae_name` `/interfaces/interface[name='interface-name']/state/admin-status` ON_CHANGE streaming supported for Junos OS and for Junos OS Evolved Release 19.1R1 and higher ON_CHANGE streaming supported `/interfaces/interface[name='interface-name']/state/counters/carrier-transitions` `/interfaces/interface[name='interface-name']/state/last-change` `/interfaces/interface[name='interface-name']/state/high-speed` `/interfaces/interface[name='interface-name']/state/counters/out-octets` `/interfaces/interface[name='interface-name']/state/counters/out-unicast-pkts` `/interfaces/interface[name='interface-name']/state/counters/out-multicast-pkts` `/interfaces/interface[name='interface-name']/state/counters/out-broadcast-pkts` `/interfaces/interface[name='interface-name']/state/counters/out-errors` `/interfaces/interface[name='interface-name']/state/counters/in-octets` `/interfaces/interface[name='interface-name']/state/counters/in-unicast-pkts` `/interfaces/interface[name='interface-name']/state/counters/in-multicast-pkts` `/interfaces/interface[name='interface-name']/state/` `/interfaces/interface[name='interface-name']/state/counters/in-broadcast-pkts` `/interfaces/interface[name='interface-name']/state/counters/in-errors` `/interfaces/interface[name='interface-name']/state/in-pause-pkts` `/interfaces/interface[name='interface-name']/state/out-pause-pkts` `/interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/` `/interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/ pkts` `/interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/bytes` `/interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/tail-drop-pkts` `/interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/ rl-drop-pkts` `/interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/ rl-drop-bytes` `/interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/avg-buffer-occupancy` `/interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/cur-buffer-occupancy` `/interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/peak-buffer-occupancy` `/interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/allocated-buffer-size` `/interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/pkts` `/interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/bytes` `/interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/tail-drop-pkts` `/interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/rl-drop-pkts` `/interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/ rl-drop-bytes` `/interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/red-drop-pkts` `/interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/red-drop-bytes` `/interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/avg-buffer-occupancy` `/interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/cur-buffer-occupancy` `/interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/ peak-buffer-occupancy` `/interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/allocated-buffer-size` `/interfaces/interface[name='interface-name']/state/description` ON_CHANGE streaming supported for Junos OS and for Junos OS Evolved Release 19.1R1 and higher `/interfaces/interface[name='interface-name']/state/enabled` `/interfaces/interface[name='interface-name']/state/ifindex` ON_CHANGE streaming supported for Junos OS Evolved Release 19.1R1 and higher `/interfaces/interface[name='interface-name']/state/last-change` `/interfaces/interface[name='interface-name']/state/mtu` `/interfaces/interface[name='interface-name']/state/name` `/interfaces/interface[name='interface-name']/state/oper-status` ON_CHANGE streaming supported for Junos OS and for Junos OS Evolved Release 19.1R1 and higher `/interfaces/interface[name='interface-name']/state/type`
`/interfaces/interface/ethernet/state/`	Sensor for physical Ethernet interface statistics. This sensor supports OpenConfig model openconfig-if-ethernet.yang (physical interface level) version 2.6.2 (no configuration). Both streaming and ON-CHANGE statistics are supported for gRPC and gNMI services. Supported on MX960, MX2020, PTX1000, and PTX5000 routers starting with Junos OS Release 19.4R1. Note: End paths supporting ON_CHANGE statistics are indicated below. `mac-address` (ON_CHANGE) `auto-negotiate` (ON_CHANGE) `duplex-mode` (ON_CHANGE) `port-speed` (ON_CHANGE) `enable-flow-control` (ON_CHANGE) `hw-mac-address` (ON_CHANGE) `negotiated-duplex-mode` (ON_CHANGE) `negotiated-port-speed` (ON_CHANGE) `counters/in-mac-control-frames` `counters/in-mac-pause-frames` `counters/in-oversize-frames` `counters/in-jabber-frames` `counters/in-fragment-frames` `counters/in-8021q-frames` `counters/in-crc-errors` `counters/in-block-errors` `counters/out-mac-control-frames` `counters/out-mac-pause-frames`
`/interfaces/interface/subinterfaces/` `/interfaces/` `interface[name='interface-name']/subinterfaces/subinterface[index='unit']/`	Sensor for logical interface traffic. Note: If a logical interface is operationally down, interface statistics continue to be exported. Note: Locally injected packets from the Routing Engine are not exported. Supported on QFX10000 switches starting with Junos OS Release 17.2R1. Supported on PTX1000 routers and EX9200 switches starting with Junos OS Release 17.3R1. Starting with Junos OS Release 18.1R1, QFX5100 switches are also supported. Starting with Junos OS Release 18.3R1, QFX5120-48Y and EX4650 switches are also supported. Starting with Junos OS Release 18.4R1, EX4600 switches are also supported. Starting with Junos OS Release 19.1R1, periodic streaming is supported on QFX10002 switches and PTX10002 routers. Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers are supported. Starting with Junos OS Release 19.2R1, periodic streaming using gNMI services is supported on QFX5110, QFX5120, QFX5200 and QFX5210 switches. Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gRPC services with PTX10008 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported. Starting with Junos OS Release 20.1R1, ON_CHANGE statistics using gNMI services with MX960, MX2020, PTX1000, and PTX5000 routers. These routers support OpenConfig model: openconfig-interfaces.yang: oc-ext:openconfig-version 2.4.1 Starting with Junos OS Release 20.2R1, streaming revenue interface statistics through Packet Forwarding Engine sensors and pseudo interface statistics through Routing Engine sensors is supported using gRPC services or gNMI services with SRX5400, SRX5600, and SRX5800 Service Gateways. Note: End paths supporting ON_CHANGE streaming are indicated. The following paths are also supported: `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/name` ON_CHANGE streaming supported. This value does not change with an event, but will be streamed on event creation and deletion. `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/ifindex` ON_CHANGE streaming supported. This value does not change with an event, but will be streamed on event creation and deletion. `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/index` ON_CHANGE streaming supported. This value does not change with an event, but will be streamed on event creation and deletion. `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/snmp_index` ON_CHANGE streaming supported starting with Junos OS Evolved Release 19.1R1 `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/admin_status` ON_CHANGE streaming supported for Junos OS and Junos OS Evolved Release 19.1R1 and higher `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oper_status` ON_CHANGE streaming supported for Junos OS and Junos OS Evolved Release 19.1R1 and higher `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/last_change` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/description` ON_CHANGE streaming supported for Junos OS and Junos OS Evolved Release 19.1R1 and higher `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/enabled` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/in_octets` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/in_unicast_pkts` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/in_broadcast_pkts` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/in_multicast_pkts` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/in_discards` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/in_errors` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/in_unknown_protos` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/out_octets` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/out_unicast_pkts` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/out_broadcast_pkts` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/out_multicast_pkts` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/out_discards` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/out_errors` `/interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/counters/last_clear`
`/interfaces/interface/`	Sensor for Routing Engine logical interface statistics (re0:mgmt-0). Starting with Junos OS Evolved Release 19.4R1, gNMI streaming for PTX10003 routers is supported. Starting with Junos OS Evolved Release 20.1R1, periodic streaming using gNMI services with PTX10008 routers is supported.
`/junos/system/linecard/optics/`	Sensor for various optical interface performance metrics, such as transmit and receive power levels. Supported on QFX10000 switches starting with Junos OS Release 17.2R1. Supported on PTX1000 routers and EX9200 switches starting with Junos OS Release 17.3R1. Supported on EX4650 switches starting with Junos OS Release 18.3R1. Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 19.2R1 on gRPC and gNMI services.
`/junos/rsvp-interface-information/`	Sensor for events and properties for RSVP interfaces. Supported on QFX5200 switches for streaming and ON_CHANGE statistics export through gNMI services starting with Junos OS Release 19.2R1. Periodic streaming using gRPC services is supported on EX4300-MP switches starting with Junos OS Release 19.4R1. You can also add the following end paths: `rsvp-interface[interface-name='ae0.100']/index` `rsvp-interface[interface-name='ae0.100']/rsvp-status` `rsvp-interface[interface-name='ae0.100']/authentication-flag` `rsvp-interface[interface-name='ae0.100']/aggregate-flag` `rsvp-interface[interface-name='ae0.100']/ack-flag` `rsvp-interface[interface-name='ae0.100']/protect-flag` `rsvp-interface[interface-name='ae0.100']/hello-interval` `rsvp-interface[interface-name='ae0.100']/interface-address` `rsvp-interface[interface-name='ae0.100']/rsvp-telink/preemption-count` `rsvp-interface[interface-name='ae0.100']/rsvp-telink/update-threshold` `rsvp-interface[interface-name='ae0.100']/rsvp-telink/subscription` `rsvp-interface[interface-name='ae0.100']/rsvp-telink/active-reservation` `rsvp-interface[interface-name='ae0.100']/rsvp-telink/static-bandwidth` `rsvp-interface[interface-name='ae0.101']/rsvp-telink/available-bandwidth`
`/junos/rsvp-interface-information/`	Sensor for events and properties for RSVP interfaces. Note: For 100 RSVP logical interfaces, configure a sampling interval equal to 60 seconds. For 200 RSVP logical interfaces, configure a sampling interval equal to 180 seconds. Supported on QFX10000 switches and QFX5200 switches starting with Junos OS Release 17.2R1. Supported on PTX1000 routers, QFX5110 switches, and EX4600 and EX9200 switches starting with Junos OS Release 17.3R1. Supported on QFX5100 switches starting with Junos OS Release 18.1R1. Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1. Supported on EX4600 switches starting with Junos OS Release 18.4R1. Periodic streaming is supported on QFX10002 switches and PTX10002 routers starting with Junos OS Release 19.1R1. You can also add the following to the end path for `/junos/rsvp-interace-information/`: `active-count` `rsvp-interface/interface-name` `rsvp-interface/index` `rsvp-interface/rsvp-status` `rsvp-interface/authentication-flag` `rsvp-interface/aggregate-flag` `rsvp-interface/ack-flag` `rsvp-interface/protect-flag` `rsvp-interface/hello-interval` `rsvp-interface/interface-address` `message-statistics/rsvp-message` `rsvp-interface/message-statistics/messages-sent` `rsvp-interface/message-statistics/messages-received` `rsvp-interrface/message-statistics/messages-sent-5seconds` `rsvp-interface/message-statistics/messages-received-5seconds` `rsvp-interface/rsvp-telink/active-reservation` `rsvp-interface/rsvp-telink/preemption-count` `rsvp-interface/rsvp-telink/update-threshold` `rsvp-interface/rsvp-telink/subscription` `rsvp-interface/rsvp-telink/static-bandwidth` `rsvp-interface/rsvp-telink/available-bandwidth` `rsvp-interface/rsvp-telink/reserved-bandwidth/bandwidth-priority` `rsvp-interface/rsvp-telink/reserved-bandwidth/total-reserved-bandwidth`
`/components/`	Sensor for operational state of Routing Engines, power supply modules, Switch Fabric Boards, Control Boards, Switch Interface Boards, Modular Interface Cards, and Physical Interface Cards. Note: Supported on QFX10000 switches and QFX5200 switches starting with Junos OS Release 17.2R1. Supported on EX9200 switches and MX150 routers starting with Junos OS Release 17.3R1. Supported on QFX5100 switches starting with Junos OS Release 18.1R1. Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1. Supported on EX4600 switches starting with Junos OS Release 18.4R1. Starting with Junos OS Release 19.2R1, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800 and vSRX are also supported. Starting with Junos OS Release 20.2R1, periodic streaming using gRPC services is supported on EX2300, EX2300-MP, and EX3400 switches. You can also add the following to each of the paths: `name` `cidx` `version` `part_number` `serial_number` `description` `clei_code` `model` `vendor_name` `properties/property/state` `properties/property/state_offline_reason` (MX Series only) `properties/property/power_usage` `properties/property/power_maximum` `properties/property/temperature_intake` `properties/property/temperature_exhaust_a` (not supported on PTX1000 and PTX3000 routers) `properties/property/temperature_exhaust_b` (not supported on PTX1000 and PTX3000 routers) `properties/property/temperature_exhaust` (not supported on PTX1000 and PTX5000 routers) `properties/property/cpu_utilization_total` `properties/property/ memory_dram_used` `properties/property/memory_utilization_heap` `properties/property/memory_utilization_buffer` `properties/property/uptime` The following paths are also supported only for Routing Engine statistics: `properties/property/mastership-state` `properties/property/mastership-priority` `properties/property/temperature-cpu` `properties/property/memory-dram-installed` `properties/property/cpu-utilization-user` `properties/property/cpu-utilization-background` `properties/property/cpu-utilization-kernel` `properties/property/cpu-utilization-idle` `properties/property/reboot-reason` The following paths are also supported for power modules: `properties/property/power-zone-upper-capacity` `properties/property/power-zone-upper-maximum` `properties/property/power-zone-upper-allocated` `properties/property/power-zone-upper-remaining` `properties/property/power-zone-upper-usage` `properties/property/power-zone-lower-capacity` `properties/property/power-zone-lower-maximum` `properties/property/power-zone-lower-allocated` `properties/property/power-zone-lower-remaining` `properties/property/power-zone-lower-usage` `properties/property/power-zone-0-capacity` `properties/property/power-zone-0-maximum` `properties/property/power-zone-0-allocated` `properties/property/power-zone-0-remaining` `properties/property/power-zone-0-usage` `properties/property/power-zone-1-capacity` `properties/property/power-zone-1-maximum` `properties/property/power-zone-1-allocated` `properties/property/power-zone-1-remaining` `properties/property/power-zone-1-usage` `properties/property/power-system-capacity` `properties/property/power-system-allocated` `properties/property/power-system-remaining` `properties/property/power-system-usage` `properties/property/temperature-ambient` The following paths are supported for either Switch Fabric Board or Control Boards or both: `properties/property/temperature-zone-0-intake` (SFB only) `properties/property/temperature-zone-0-intake-a` (both SFB and CB) `properties/property/temperature-zone-1-intake-b` (both SFB and CB) `properties/property/temperature-zone-0-exhaust` (SFB only) `properties/property/temperature-zone-1-exhaust` (SFB only) `properties/property/temperature-zone-0-intake-c` (CB only) `properties/property/temperature-zone-0-exhaust-a` (CB only) `properties/property/temperature-zone-1-exhaust-b` (CB only)
`/lacp/`	Sensor for operational state of aggregated Ethernet interfaces configured with the Link Aggregation Control Protocol. Supported on QFX10000 switches and QFX5200 switches starting with Junos OS Release 17.2R1. Supported on PTX1000 routers and EX9200 switches starting with Junos OS Release 17.3R1. Supported on QFX5100 switches starting with Junos OS Release 18.1R1. Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1. Supported on EX4600 switches starting with unos OS Release 18.4R1, Supported on PTX10003 routers starting with Junos OS Evolved Release 19.1R1. Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gRPC services with PTX10008 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported. Starting with Junos OS Release 20.2R1, periodic streaming using gRPC services is supported on EX2300, EX2300-MP, and EX3400 switches. You can also add the following to the end of the path for `/lacp/`: `interfaces/interface/state` `interfaces/interface/members/member/state/activity` `interfaces/interface/members/member/state/timeout` `interfaces/interface/members/member/state/system-id` `interfaces/interface/members/member/state/partner-id` `interfaces/interface/members/member/state/interface` `interfaces/interface/members/member/state/synchronization` `interfaces/interface/members/member/state/aggregatable` `interfaces/interface/members/member/state/collecting` `interfaces/interface/members/member/state/distributing` `interfaces/interface/members/member/state/oper-key` `interfaces/interface/members/member/state/partner-key` `interfaces/interface/members/member/state/counters/lacp-in-packets` `interfaces/interface/members/member/state/counters/lacp-out-packets` `interfaces/interface/members/member/state/counters/lacp-rx-errors` `interfaces/interface/members/member/state/counters/lacp-unknown-errors` `interfaces/interface/members/member/state/counters/lacp-errors` `state/system-priority` `interfaces/interface[name='aggregate-interface-name']/state/` `interfaces/interface[name='aggregate-interface-name'] /members/member[interface='interface-name']/state/` `interfaces/interface[name='aggregate-interface-name'] /members/member[interface='interface-name']/state/counters/` `interfaces/interface[name='aggregate-interface-name'] /members/member[interface='interface-name']/state/port-num` `interfaces/interface[name='aggregate-interface-name'] /members/member[interface='interface-name']/state/partner-port-num` `interfaces/interface[name='aggregate-interface-name'] /members/member[interface='interface-name']/state/mux-state`
`/lldp/`	Sensor for operational state of Ethernet interfaces enabled with the Link Layer Discovery Protocol. Subscriptions using gNMI services that include the resource path `/lldp/interfaces/interface/neighbors/neighbor/state/` do not export TTL value statistics to the collector. These statistics can be observed through the Junos CLI using the operational mode command `show lldp neighbors interface interface-name`. Supported on QFX10000 switches and QFX5200 switches starting with Junos OS Release 17.2R1. Supported on PTX1000 routers and EX9200, EX4600, and QFX5110 switches starting with Junos OS Release 17.3R1. Supported on QFX5100 switches starting with Junos OS Release 18.1R1. Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1. Supported on EX4600 switches starting with Junos OS Release 18.4R1. ON_CHANGE streaming is supported on MX Series and PTX Series routers, starting with Junos OS Release 18.3R1. Starting with Junos OS Release 19.1R1, periodic streaming on QFX10002 switches and PTX10002 routers is supported. Supported on SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800 and vSRX starting with Junos OS Release 19.2R1. Supported on PTX10003 routers starting with Junos OS Evolved Release 19.1R1. The resource path `/lldp/interfaces/interface[name='xe-0/0/9']/` is supported on QFX5200 switches for streaming and ON_CHANGE statistics export through gNMI services starting with Junos OS Release 19.2R1. QFX5200 switches support the LLDP statistics export and OpenConfig LLDP Model (v0.1.0). Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gRPC services with PTX10008 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported. Starting with Junos OS Release 20.1R1, periodic streaming using gRPC services with MX240, MX480, MX960, MX10003, PTX10008, and PTX10016 routers is supported for leaf-list `suppress-tlv-advertisement` under the resource path /lldp/state/suppress-tlv-advertisement. The resource path `/lldp/interfaces/interface[name='name']/` is supported on EX2300, EX2300-MP, and EX3400 switches periodic streaming using gNMI services starting with Junos OS Release 20.2R1. Starting with Junos OS Release 20.2R1, streaming pseudo interface statistics through Routing Engine sensors is supported using gRPC services or gNMI services with SRX5400, SRX5600, and SRX5800 Service Gateways. Previously, streaming statistics was only supported through gRPC services. You can also add the following to the end of the path for `/lldp/`: Note: End paths supporting ON_CHANGE streaming are indicated. `state/` `state/enabled/` ON_CHANGE streaming supported `state/hello-timer/` ON_CHANGE streaming supported `state/chassis-id/` ON_CHANGE streaming supported `state/chassis-id-type/` ON_CHANGE streaming supported /state/suppress-tlv-advertisement gRPC streaming with MX240, MX480, MX960, MX10003, PTX10008, and PTX10016 routers is supported for this attribute. The TLVs `port-description`, `system-name`, `system-description`, `system-capabilities`, and `management address` are streamed to support operational state, notifications, and configuration change support. `state/system-name/` ON_CHANGE streaming supported `state/system-description/` ON_CHANGE streaming supported `state/loc-port-id-type/` `state/counters/frame-in/` `state/counters/frame-out/` `state/counters/frame-error-in/` `state/counters/frame-discard/` `state/counters/tlv-unknown/` `state/counters/tlv-discard/` `state/counters/tlv-accepted/` `state/counters/entries-aged-out/` `state/counters/last-clear/` `interfaces/interface[name='interface-name']/` `interfaces/interface[name='interface-name']/state/` `interfaces/interface[name='interface-name']/state/name/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/state/enabled/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/state/loc-port-id/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/state/loc-port-description/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/state/counters/frame-in/` `interfaces/interface[name='interface-name']/state/counters/frame-error-in/` `interfaces/interface[name='interface-name']/state/counters/frame-discard/` `interfaces/interface[name='interface-name']/state/counters/tlv-discard/` `interfaces/interface[name='interface-name']/state/counters/tlv-unknown/` `interfaces/interface[name='interface-name']/state/counters/frame-out/` `interfaces/interface[name='interface-name']/state/counters/frame-error-out/` `interfaces/interface[name='interface-name']/state/counters/last-clear/` `interfaces/interface[name='interface-name']/neighbors/neighbor/` `interfaces/interface[name='interface-name']/neighbors/neighbor/capabilities/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/capabilities/cabapility/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/capabilities/cabapility/name/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/capabilities/cabapility/state/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/capabilities/cabapility/state/name/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/capabilities/cabapility/state/enabled/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/custom-tlvs/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/custom-tlvs/tlv/` `interfaces/interface[name='interface-name']/neighbors/neighbor/custom-tlvs/tlv/type/` `interfaces/interface[name='interface-name']/neighbors/neighbor/custom-tlvs/tlv/oui/` `interfaces/interface[name='interface-name']/neighbors/neighbor/custom-tlvs/tlv/oui-subtype/` `interfaces/interface[name='interface-name']/neighbors/neighbor/custom-tlvs/tlv/state/` `interfaces/interface[name='interface-name']/neighbors/neighbor/custom-tlvs/tlv/state/type/` `interfaces/interface[name='interface-name']/neighbors/neighbor/custom-tlvs/tlv/state/oui/` `interfaces/interface[name='interface-name']/neighbors/neighbor/custom-tlvs/tlv/state/oui-subtype/` `interfaces/interface[name='interface-name']/neighbors/neighbor/custom-tlvs/tlv/state/value/` `interfaces/interface[name='interface-name']/neighbors/neighbor/state/system-name/` ON_CHANGE streaming supported. This resource path does not change with an event, but will be streamed on creation and deletion. `interfaces/interface[name='interface-name']/neighbors/neighbor/state/system-description/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/state/chassis-id/` ON_CHANGE streaming supported. This resource path does not change with an event, but will be streamed on creation and deletion. `interfaces/interface[name='interface-name']/neighbors/neighbor/state/chassis-id-type/` ON_CHANGE streaming supported. This resource path does not change with an event, but will be streamed on creation and deletion. `interfaces/interface[name='interface-name']/neighbors/neighbor/state/id/` `interfaces/interface[name='interface-name']/neighbors/neighbor/state/age/` ON_CHANGE streaming supported Note: This attribute is not sent for every LLDP PDU because it continuously changes. The `age` value is sent when another attribute learned by the neighbor is updated. `interfaces/interface[name='interface-name']/neighbors/neighbor/state/last-update/` ON_CHANGE streaming supported This attribute is not sent for every LLDP PDU because it continuously changes. The `last-update` value is sent when another attribute learned by the neighbor is updated. `interfaces/interface[name='interface-name']/neighbors/neighbor/state/port-id/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/state/port-id-type/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/state/port-description/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/state/management-address/` ON_CHANGE streaming supported `interfaces/interface[name='interface-name']/neighbors/neighbor/state/management-address-type/` ON_CHANGE streaming supported
`/mpls/lsps/constrained-path/tunnels/tunnel[name='foo-name',source='foo-source']/p2p-tunnel-attributes/p2p-primary-paths[name='foo-path']/lsp-instances[index='local-index']/state/notify-status`	Sensor to export events for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs. ON_CHANGE support for LSP events is only activated when the reporting interval is set to 0 in the subscription request. This sensor is supported on indicated platforms up to and including Junos OS Release 17.3R1. See the following resource paths for LSP support in Junos OS Release 17.4R1 and higher: `/network-instances/network-instance[name='instance-name']/mpls/lsps/constrained-path/tunnels/tunnel/p2p-tunnel-attributes/p2p-primary-paths/p2p-primary-path` `/network-instances/network-instance[name='instance-name']/mpls/signaling-protocols/rsvp-te/sessions/session/state/notify-status` Supported on PTX Series routers, MX Series routers , and QFX10002, QFX10008, and QFX10016 switches starting with Junos OS Release 17.2R1. The following events are exported under this resource path: `INITIATED` `CONCLUDED_UP` `CONCLUDED_TORN_DOWN` `PROTECTION_AVAILABLE` `PROTECTION_UNAVAILABLE` `AUTOBW_SUCCESS` `AUTOBW_FAIL` `TUNNEL_LOCAL_REPAIRED` `PATHERR_RECEIVED` `ADMISSION_CONTROL_FAILURE` `SESSION_PREEMPTED` `BAD_LOOSE_ROUTE` `BAD_STRICT_ROUTE` `LABEL_ALLOCATION_FAILURE` `ROUTING_LOOP_DETECTED` `REQUESTED_BANDWIDTH_UNAVAILABLE`
`/mpls/lsps/constrained-path/tunnels/tunnel[name='foo-name',source='foo-source']/p2p-tunnel-attributes/p2p-primary-paths[name='foo-path']/state/notify-status`	Sensor to export events for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs. ON_CHANGE support for LSP events is only activated when the reporting interval is set to 0 in the subscription request. This sensor is supported on indicated platforms up to and including Junos OS Release 17.3R1. See the following resource paths for LSP support in Junos OS Release 17.4R1 and higher: `/network-instances/network-instance[name='instance-name']/mpls/lsps-constrained-path/tunnels/tunnel/p2p-tunnel-attributes/p2p-primary-paths/p2p-primary-path` `/network-instances/network-instance[name='instance-name']/mpls/signaling-protocols/rsvp-te/sessions/session/state/notify-status` Supported on PTX Series routers, MX Series routers , and QFX10002, QFX10008, and QFX10016 switches starting with Junos OS Release 17.2R1. The following events are exported under this resource path: `DESELECT_ACTIVE_PATH` `CHANGE_ACTIVE_PATH` `SELECT_ACTIVE_PATH` `ORIGINATE_MBB` `CSPF_NO_ROUTE` `CSPF_SUCCESS` `RESTART_RECOVERY_FAIL`
`/mpls/lsps-constrained-path/tunnels/tunnel[name='foo-name',source='foo-source']/p2p-tunnel-attributes/p2p-primary-paths[name='foo-path']/state/name`	Sensor to export the path name for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs. This sensor is supported on indicated platforms up to and including Junos OS Release 17.3R1. See the following resource paths for LSP support in Junos OS Release 17.4R1 and higher: `/network-instances/network-instance[name='instance-name']/mpls/lsps-constrained-path/tunnels/tunnel/p2p-tunnel-attributes/p2p-primary-paths/` `/network-instances/network-instance[name='instance-name']/mpls/signaling-protocols/rsvp-te/sessions/session/state/notify-status` Supported on PTX Series routers, MX Series routers , and QFX10002, QFX10008, and QFX10016 switches starting with Junos OS Release 17.2R1.
`/mpls/lsps-constrained-path/tunnels/tunnel[name='foo-name',source='foo-source']/p2p-tunnel-attributes/p2p-primary-paths[name='foo-path']/lsp-instances[index='local-index']/state/`	Sensor to export LSP properties for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs Supported on PTX Series routers, MX Series routers, and QFX10002, QFX10008, and QFX10016 switches starting with Junos OS Release 17.2R1. The following end paths are also supported for the resource path: `bandwidth` `metric` `max-average-bandwidth` `explicit-route-objects` `record-route-objects`
`/mpls/signaling-protocols/ldp/lsp-transit-policies/lsp-transit-policy/state/counters`	Sensor to export statistics for LDP LSP transit traffic. Supported on MX Series routers starting with Junos OS Release 20.2R1.
`/mpls/signaling-protocols/ldp/lsp-ingress-policies/lsp-ingress-policy/state/counters`	Sensor to export statistics for LDP LSP ingress traffic. Supported on MX Series routers starting with Junos OS Release 20.2R1.
`/mpls/signaling-protocols/ldp/p2mp-lsps/p2mp-lsp/state/counters`	Sensor to export statistics for multipoint LDP LSP traffic. Supported on MX Series routers starting with Junos OS Release 20.2R1.
`/mpls/signalling-protocols/ldp/p2mp-interfaces/p2mp-interface/state/counters/`	Sensor to export statistics for multipoint LDP egress traffic per interface. Supported on MX Series routers starting with Junos OS Release 20.2R1.
`/mpls/signalling-protocols/ldp/p2mp-egress-interfaces/p2mp-interface/state/counters/`	Sensor to export statistics for multipoint LDP egress traffic per interface. Supported only on MPC10E-10C-MRATE, MPC10E-15C-MRATE, and MX2K-MPC11E line cards line cards on MX Series routers starting with Junos OS Release 20.3R1.
`/mpls/signalling-protocols/ldp/p2mp-interfaces/p2mp-interface/`	Sensor to export statistics for multipoint LDP ingress traffic per interface. Supported on MX Series routers starting with Junos OS Release 20.2R1.
`/mpls/lsps/signaling-protocols/rsvp-te/sessions/session[local-index='foo-index']/state/notify-status`	Sensor to export statistics for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs. ON_CHANGE support for LSP events is only activated when the reporting interval is set to 0 in the subscription request. Supported on PTX Series routers, MX Series routers, and QFX10002, QFX10008, and QFX10016 switches starting with Junos OS Release 17.2R1. The following events are exported under this resource path: `PATHERR_RECEIVED` `TTL_EXPIRED` `NON_RSVP_CAPABLE_ROUTER` `RESVTEAR_RECEIVED` `PATH_MTU_CHANGE`
`/network-instances/network-instance/mpls/signaling-protocols/rsvp-te/`	Sensor to export events for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs. Starting in Junos OS Evolved Release 19.2R1, PTX10003 routers support streaming statistics. The following end paths are also supported: `interface-attributes/interface/bandwidth-reservations/state/active-reservations-count` `interface-attributes/interface/bandwidth-reservations/state/available-bandwidth` `interface-attributes/interface/bandwidth-reservations/state/highwater-mark` `interface-attributes/interface/bandwidth-reservations/state/reserved-bandwidth` `interface-attributes/interface/counters/in-ack-messages` `interface-attributes/interface/counters/in-hello-messages` `interface-attributes/interface/counters/in-path-messages` `interface-attributes/interface/counters/in-path-tear-messages` `interface-attributes/interface/counters/in-reservation-error-messages` `interface-attributes/interface/counters/in-reservation-messages` `interface-attributes/interface/counters/in-reservation-tear-messages` `interface-attributes/interface/counters/in-srefresh-messages` `interface-attributes/interface/counters/out-path-tear-messages` `interface-attributes/interface/counters/out-ack-messages` `interface-attributes/interface/counters/out-hello-messages` `interface-attributes/interface/counters/out-path-messages` `interface-attributes/interface/counters/out-reservation-error-messages` `interface-attributes/interface/counters/out-reservation-messages` `interface-attributes/interface/counters/out-reservation-tear-messages` `interface-attributes/interface/counters/out-srefresh-messages` `neighbors/neighbor/state/neighbor-status` `sessions/session/record-route-objects/record-route-object` `sessions/session/state/destination-address` `sessions/session/state/label-in` `sessions/session/state/label-out` `sessions/session/state/lsp-id`
`/network-instances/network-instance/mpls/signaling-protocols/rsvp-te/sessions/session/state/notify-status`	Supported on Junos OS Release through 17.4R1 and higher. Sensor to export events for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs. ON_CHANGE support for LSP events is only activated when the reporting interval is set to 0 in the subscription request. Supported on PTX Series routers, MX Series routers, and QFX10002, QFX10008, and QFX10016 switches starting with Junos OS Release 17.2R1. The following events are exported under this resource path: `DETOUR-UP` `DETOUR-DOWN` `PATHERR-RECV` `PATHERR-RECV/ADMISSION_CONTROL_FAILURE` `PATHERR-RECV/SESSION_PREEMPTED` `PATHERR-RECV/BAD_LOOSE_ROUTE` `PATHERR-RECV/BAD_STRICT_ROUTE` `PATHERR-RECV/LABEL_ALLOCATION_FAILURE` `PATHERR-RECV/NON_RSVP_CAPABLE_ROUTER` `PATHERR-RECV/TTL_EXPIRED` `PATHERR-RECV/ROUTING_LOOP_DETECTED` `PATHERR-RECV/REQUESTED_BANDWIDTH_UNAVAILABLE` `PATHMTU-CHANGE`
`/mpls/signaling-protocols/segment-routing/`	Sensor for traffic statistics for both ingress IP traffic and transit MPLS traffic.. Supported on MX Series and PTX Series routers starting with Junos OS Release 18.3R1. The following end points are also supported and specify BGP Segment Routing traffic Engineering (SR-TE) transit statistics: `/sr-te-bsid-policies/sr-te-bsid-policy[binding-sid=‘80001’, to-address=’foo-to' color=’foo-color’]/state/counters[name=’oc-xxx’]/packets` `/sr-te-bsid-policies/sr-te-bsid-policy[binding-sid=‘80001’, to-address=’foo-to' color=’foo-color’]/state/counters[name=’oc-xxx’]/bytes` The following end points are also supported and specify BGP Segment Routing traffic Engineering (SR-TE) ingress statistics: `/sr-te-ip-policies/sr-te-ip-policy[to-address=’foo-to' color=’foo-color’]/state/counters[name=’oc-xxx’]/packets` `/sr-te-ip-policies/sr-te-ip-policy[to-address=’foo-to' color=’foo-color’]/state/counters[name=’oc-xxx’]/bytes` In addition to configuring the sensor, you must enable statistics collection using the statistics statement at the [`[edit protocols source-packet-routing telemetry statistics`] hierarchy level.
`/arp-information/`	Sensor for Address Resolution Protocol (ARP) statistics for IPv4 routes. Supported on QFX10000 and QFX5200 switches switches starting with Junos OS Release 17.2R1. Supported on PTX1000 routers, EX9200 switches, and MX150 routers starting with Junos OS Release 17.3R1. Supported on QFX5100 switches starting with Junos OS Release 18.1R1. Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1. Supported on EX4600 switches starting with Junos OS Release 18.4R1. Periodic streaming is supported on QFX10002 switches and PTX10002 routers starting with Junos OS Release 19.1R1, Supported on SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800 and vSRX starting with Junos OS Release 19.2R1. Supported on PTX10003 routers starting with Junos OS Evolved Release 19.1R1. Starting with Junos OS Release 19.2R1, gNMI streaming and ON_CHANGE for QFX5200 switches is supported. Starting with Junos OS Release 19.3R1, gNMI streaming and ON_CHANGE for MX960, MX2010, MX2020, PTX5000, PTX1000, and PTX10000 routers is supported. Starting with Junos OS Evolved Release 19.4R1, gNMI streaming for PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gRPC services with PTX10008 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported. Starting with Junos OS Evolved Release 20.1R1, periodic streaming using gNMI services with PTX10008 routers is supported. Starting with Junos OS Release 20.2R1, periodic streaming using gRPC services with EX2300, EX2300-MP, and EX3400 switches is supported. Starting with Junos OS Release 20.2R1, streaming pseudo interface statistics through Routing Engine sensors is supported using gRPC services or gNMI services with SRX5400, SRX5600, and SRX5800 Service Gateways. Previously, streaming statistics was only supported through gRPC services. You can also add the following to the end path for `/arp-information/` `ipv4` `ipv4/neighbors` `ipv4/neighbors/neighbor` `ipv4/neighbors/neighbor/state/host-name` `ipv4/neighbors/neighbor/state/table-id` `ipv4/neighbors/neighbor/state/neighbor-state` `ipv4/neighbors/neighbor/state/expiry` `ipv4/neighbors/neighbor/state/ispublish` `ipv4/neighbors/neighbor/state/interface-name` `ipv4/neighbors/neighbor/state/logical-router-id`
`/interfaces/interface[name='interface-name']/`	Sensor for Routing Engine internal interfaces. Note: On MX Series routers, you can specify the following interfaces: fxp0, em0, and em1 On PTX Series routers, you can specify the following interfaces: em0, ixlv0, ixlv1 On PTX Series routers with dual Routing Engines, you can specify the following interfaces: em0, ixgbe0, ixgbe1 On PTX10003 routers with Junos OS Evolved Release 19.1R1, you can specify the following interfaces: re0:mgmt-0. No internal interfaces are supported. Support on PTX1000 routers starting with Junos OS Release 17.3R1. Support on PTX10003 routers starting in Junos OS Evolved Release 19.1R1. The following end paths are also supported: `interfaces/interface/state/type` `/interfaces/interface/state/mtu` `/interfaces/interface/state/name` `/interfaces/interface/state/description` `/interfaces/interface/state/enabled` `/interfaces/interface/state/ifindex` `/interfaces/interface/state/admin-status` `/interfaces/interface/state/oper-status` `/interfaces/interface/state/last-change` `/interfaces/interface/state/speed` `/interfaces/interface/state/counters/in-octets` `/interfaces/interface/state/counters/in-unicast-pkts` `/interfaces/interface/state/counters/in-broadcast-pkts` `/interfaces/interface/state/counters/in-multicast-pkts` `/interfaces/interface/state/counters/in-discards` `/interfaces/interface/state/counters/in-errors` `/interfaces/interface/state/counters/in-unknown-protos` `/interfaces/interface/state/counters/out-octets` `/interfaces/interface/state/counters/out-unicast-pkts` `/interfaces/interface/state/counters/out-broadcast-pkts` `/interfaces/interface/state/counters/out-multicast-pkts` `/interfaces/interface/state/counters/out-discards` `/interfaces/interface/state/counters/out-errors` `/interfaces/interface/state/counters/last-clear` `/interfaces/interface/state/counters/in-pkts` `/interfaces/interface/state/counters/in-sec-pkts` `/interfaces/interface/state/counters/in-sec-octets` `/interfaces/interface/state/counters/in-pause-pkts` `/interfaces/interface/state/counters/out-pkts` `/interfaces/interface/state/counters/out-sec-pkts` `/interfaces/interface/state/counters/out-sec-octets` `/interfaces/interface/state/counters/out-pause-pkts` `/interfaces/interface/state/counters/in-drops` `/interfaces/interface/state/counters/in-frame-errors` `/interfaces/interface/state/counters/in-runts` `/interfaces/interface/state/counters/in-lchan-errors` `/interfaces/interface/state/counters/in-l-mismatch-errors` `/interfaces/interface/state/counters/in-fifo-errors` `/interfaces/interface/state/counters/in-giants` `/interfaces/interface/state/counters/in-resource-errors` `/interfaces/interface/state/counters/out-drops` `/interfaces/interface/state/counters/carrier-transitions` `/interfaces/interface/state/counters/mtu-errors` `/interfaces/interface/state/counters/out-resource-errors` `/interfaces/interface/subinterfaces/subinterface/index` `/interfaces/interface/subinterfaces/subinterface/state/index` `/interfaces/interface/subinterfaces/subinterface/state/name` `/interfaces/interface/subinterfaces/subinterface/state/description` `/interfaces/interface/subinterfaces/subinterface/state/enabled` `/interfaces/interface/subinterfaces/subinterface/state/ifindex` `/interfaces/interface/subinterfaces/subinterface/state/admin-status` `/interfaces/interface/subinterfaces/subinterface/state/oper-status` `/interfaces/interface/subinterfaces/subinterface/state/last-change` `/interfaces/interface/subinterfaces/subinterface/state/counters/in-pkts` `/interfaces/interface/subinterfaces/subinterface/state/counters/in-octets` `/interfaces/interface/subinterfaces/subinterface/state/counters/in-unicast-pkts` `/interfaces/interface/subinterfaces/subinterface/state/counters/in-broadcast-pkts` `/interfaces/interface/subinterfaces/subinterface/state/counters/in-multicast-pkts` `/interfaces/interface/subinterfaces/subinterface/state/counters/in-discards` `/interfaces/interface/subinterfaces/subinterface/state/counters/in-errors` `/interfaces/interface/subinterfaces/subinterface/state/counters/in-unknown-protos` `/interfaces/interface/subinterfaces/subinterface/state/counters/out-octets` `/interfaces/interface/subinterfaces/subinterface/state/counters/out-unicast-pkts` `/interfaces/interface/subinterfaces/subinterface/state/counters/out-broadcast-pkts` `/interfaces/interface/subinterfaces/subinterface/state/counters/out-multicast-pkts` `/interfaces/interface/subinterfaces/subinterface/state/counters/out-discards` `/interfaces/interface/subinterfaces/subinterface/state/counters/out-errors` `/interfaces/interface/subinterfaces/subinterface/state/counters/last-clear` `/interfaces/interface/subinterfaces/subinterface/state/counters/out-pkts`
`/nd6-information/`	Sensor for Network Discovery Protocol (NDP) table state information for IPv6 routes. Supported on QFX10000 and QFX5200 switches starting with Junos OS Release 17.2R1. Supported on PTX1000 routers, EX9200 switches, and MX150 routers starting with Junos OS Release 17.3R1. Supported on QFX5100 switches starting with Junos OS Release 18.1R1. Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1. Supported on EX4600 switches starting with Junos OS Release 18.4R1. Supported on PTX10003 routers starting with Junos OS Evolved Release 19.1R1. Supported on SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800 and vSRX starting with Junos OS Release 19.2R1, gNMI streaming and ON_CHANGE for QFX5200 switches is supported on Junos OS Release starting with 19.2R1. gNMI streaming and ON_CHANGE for MX960, MX2010, MX2020, PTX5000, PTX1000, and PTX10000 routers is supported starting with with Junos OS Release 19.3R1. Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported. Starting with Junos OS Evolved Release 19.4R1, gNMI streaming for PTX10003 routers is supported. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gRPC services with PTX10008 routers is supported. Starting with Junos OS Evolved Release 20.1R1, periodic streaming using gNMI services with PTX10008 routers is supported. Starting with Junos OS Release 20.2R1, periodic streaming using gRPC services with EX2300, EX2300-MP, and EX3400 switches is supported. Starting with Junos OS Release 20.2R1, periodic streaming using gRPC services with PTX10001 routers is supported. Starting with Junos OS Release 20.2R1, streaming pseudo interface statistics through Routing Engine sensors is supported using gRPC services or gNMI services with SRX5400, SRX5600, and SRX5800 Service Gateways. Previously, streaming statistics was only supported through gRPC services. You can also add the following to the end path for `nd6-information/` `ipv6/neighbors/neighbor/state/ip` ON_CHANGE streaming supported starting with Junos OS Evolved Release 19.1R1 `ipv6/neighbors/neighbor/state/link-layer-address` ON_CHANGE streaming supported starting with Junos OS Evolved Release 19.1R1 `ipv6/neighbors/neighbor/state/origin` `ipv6/neighbors/neighbor/sttae/is-router` ON_CHANGE streaming supported starting with Junos OS Evolved Release 19.1R1 `ipv6/neighbors/neighbor/state/neighbor-state` `ipv6/neighbors/neighbor/state/table-id` `ipv6/neighbors/neighbor/state/is-secure` `ipv6/neighbors/neighbor/state/is-publish` `ipv6/neighbors/neighbor/state/expiry` `ipv6/neighbors/neighbor/state/interface-name` `ipv6/neighbors/neighbor/state/logical-router-id`
`/ipv6-ra/`	Sensor for NDP router-advertisement statistics. Starting with Junos OS Release 19.2R1, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800 and vSRX are supported. Starting with Junos OS Release 19.2R1, gNMI streaming and ON_CHANGE for QFX5200 switches is supported. Starting with Junos OS Release 19.3R1, gNMI streaming and ON_CHANGE for MX960, MX2010, MX2020, PTX5000, PTX1000, and PTX10000 routers is supported. Starting with Junos OS Evolved Release 20.2R1, periodic streaming using gRPC services with PTX10001 routers is supported. Starting with Junos OS Release 20.2R1, streaming pseudo interface statistics through Routing Engine sensors is supported using gRPC services or gNMI services with SRX5400, SRX5600, and SRX5800 Service Gateways. Previously, streaming statistics was only supported through gRPC services.
`/junos/system/linecard/packet/usage/`	Sensor for Packet Forwarding Engine Statistics. This sensor exports statistics for counters and provides visibility into Packet Forwarding Engine error and drop statistics. This sensor is supported starting on MX Series and PTX Series routers starting with Junos OS Release 17.4R1. Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers are supported. Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services. Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.
`/junos/system/linecard/packet/usage/`	Sensor for Packet Forwarding Engine Statistics. This sensor exports statistics and provides visibility into Packet Forwarding Engine error and drop statistics. Statistics include counters (CC, CPU, and NPU) for traffic data. Note that NPU statistics are different than those streamed from the sensors /junos/system/linecard/npu/memory/ and /junos/system/linecard/npu/utilization/ . Sensor output is comparable to the output using the operational mode command `show pfe statistics traffic`. Shown below, statistics are exported for the default FPC (FPC0). Multiples FPCs are supported. The component values and property values are names (like interface names). Starting in Junos OS Evolved Release 19.4R1, streaming statistics using gRPC and gNMI services on PTX10008 routers is supported. Starting in Junos OS Release 20.2R1, INITIAL_SYNC statistics using gNMI services on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches are supported. The following paths are also supported: `:/components/component[name='FPC0:CC0']/properties/property[name='ts-input-packets']/` `/components/component[name='FPC0:CC0']/properties/property[name='ts-output-packets']/` /`/components/component[name='FPC0:CC0']/properties/property[name='ts-input-packets-pps']/` `/components/component[name='FPC0:CC0']/properties/property[name='ts-output-packets-pps']/` `/components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-input-packets']/` `/components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-input-packets-pps']/` `/components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-output-packets']/` `/components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-output-packets-pps']/` `/components/component[name='FPC0:CPU0']/properties/property[name='lts-input-packets']/` `/components/component[name='FPC0:CPU0']/properties/property[name='lts-output-packets']/` `/components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-control-drops']/` `/components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-high-drops']/` `/components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-medium-drops']/` `/components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-low-drops']/` `/components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-output-low-drops']/` `/components/component[name='FPC0:CPU0']/properties/property[name='lts-hw-input-drops']/` `/components/component[name='FPC0:NPU0']/properties/property[name='hwdsNormal']/` `/components/component[name='FPC0:NPU0']/properties/property[name='hwds-data-error']/` `/components/component[name='FPC0:NPU0']/properties/property[name='hwds-tcp-error']/` `/components/component[name='FPC0:NPU0']/properties/property[name='hwds-illegal-nh']/` `/components/component[name='FPC0:NPU0']/properties/property[name='hwds-invalid-iif']/` /`/components/component[name='FPC0:NPU0']/properties/property[name='hwds-fabric']/`
`/network-instances/network-instance/protocols/protocol/isis/levels/level/` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/`	Sensor for IS-IS routing protocol statistics. Statistics are exported separately for each routing instance. To specify a routing-instance name: /`network-instances/network-instance[name_'instance-name']/protocols/protocol/isis/levels/level/` `/network-instances/network-instance[name_'instance-name']/protocols/protocol/isis/interfaces/interface/levels/level/` Note: This sensor is supported on MX Series and PTX Series routers starting with Junos OS Release 17.4R1. Starting with Junos OS Release 19.2R1, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800 and vSRX are also supported. Starting with Junos OS Release 20.2R1, streaming pseudo interface statistics through Routing Engine sensors is supported using gRPC services or gNMI services with SRX5400, SRX5600, and SRX5800 Service Gateways. Previously, streaming statistics was only supported through gRPC services. The following paths are also supported: `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/lsp/received` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/lsp/processed` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/lsp/dropped` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/lsp/sent` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/lsp/retransmit` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/iih/received` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/iih/processed` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/iih/dropped` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/iih/sent` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/iih/retransmit` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/psnp/received` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/psnp/processed` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/psnp/dropped` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/psnp/sent` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/psnp/retransmit` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/cnsp/received` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/cnsp/processed` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/cnsp/dropped` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/packet-counters/cnsp/sent` `/network-instances/network-instance/protocols/protocol/isis/levels/level/system-level-counters/state/corrupted-lsps` `/network-instances/network-instance/protocols/protocol/isis/levels/level/system-level-counters/state/database-overloads` `/network-instances/network-instance/protocols/protocol/isis/levels/level/system-level-counters/state/manual-address-drop-from-area` `/network-instances/network-instance/protocols/protocol/ isis/levels/level/system-level-counters/state/exceeded-max-seq-nums` `/network-instances/network-instance/protocols/protocol/isis/levels/level/system-level-counters/state/seq-num-skips` `/network-instances/network-instance/protocols/protocol/isis/levels/level/system-level-counters/state/own-lsp-purges` `/network-instances/network-instance/protocols/protocol/ isis/levels/level/system-level-counters/state/id-len-mismatch` `/network-instances/network-instance/protocols/protocol/isis/levels/level/system-level-counters/state/part-changes` `/network-instances/network-instance/protocols/protocol/ isis/levels/level/system-level-counters/state/max-area-address-mismatches` `/network-instances/network-instance/protocols/protocol/isis/levels/level/system-level-counters/state/auth-fails` `/network-instances/network-instance/protocols/protocol/isis/levels/level/system-level-counters/state/spf-runs` `/network-instances/network-instance/protocols/protocol/isis/levels/level/system-level-counters/state/auth-type-fails` `/network-instances/network-instance/protocols/protocol/isis/levels/level/system-level-counters/state/lsp-errors` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/circuit-counters/state/adj-changes` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/circuit-counters/state/adj-number` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/circuit-counters/state/auth-fails` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/circuit-counters/state/auth-type-fails` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/circuit-counters/state/id-field-len-mismatches` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/circuit-counters/state/lan-dis-changes` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/circuit-counters/state/max-area-address-mismatch` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/circuit-counters/state/rejected-adj` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/system-id` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/dis-system-id` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/local-extended-system-id` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/neighbor-extended-system-id` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/adjacency-state` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/neighbor-circuit-type` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/neighbor-ipv4-address` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/neighbor-ipv6-address` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/neighbor-snpa` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/levels/level/adjacencies/adjacency/state/priority` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/remaining-hold-time` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/restart-status` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/restart-support` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/restart-suppress` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/up-time` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/nlpid` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/adjacencies/adjacency/state/area-address` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/topologies` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/multi-topology` `/network-instances/network-instance/protocols/protocol/isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/adjacency-type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/state/ipv4-prefix` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/state/up-down` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/state/s-bit` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/state/metric` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/flags/state/flags` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/flags/state/ipv4-source-router-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/ipv6-source-router-id/state/ipv6-source-router-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/flags/state/tag64` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/flags/state/tag32` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/length` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sid/sid/state/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/flags/state/flags` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/flags/state/algorithm` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/state/ipv6-prefix` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/state/up-down` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/state/s-bit` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/state/x-bit` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/state/metric` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/state/ipv6-prefix` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/ipv4-source-router-id/state/ipv4-source-router-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/ipv6-source-router-id/state/ipv6-source-router-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/tag64/state/tag64` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/tag64/state/tag32` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/length` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sid/sid/state/value` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sid/sid/state/flags` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sid/sid/state/algorithm` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/router-capability/state/flags` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/tlvs/tlv/router-capabilities/router-capability/state/rtr-id` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/undefined-tlvs/undefined-tlv/state/type` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/undefined-tlvs/undefined-tlv/state/length` `/network-instances/network-instance/protocols/protocol/isis/levels/level/link-state-database/lsp/undefined-tlvs/undefined-tlv/state/value`
`/junos/services/segment-routing/interface/ingress/usage/` `/junos/services/segment-routing/interface/egress/usage/` `/junos/services/segment-routing/sid/usage/`	Sensors for aggregate segment routing traffic with IS-IS. This sensor is supported on MX Series and PTX5000 routers starting with Junos OS Release 17.4R1. Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services. Statistics are exported separately for each routing instance. The first path exports inbound traffic. The second path exports outbound traffic. The third path exports inbound segment routing traffic for each segment identifier. Note: When you enable a sensor for segment routing statistics, you must also configure the `sensor-based-stats` statement at the `[edit protocols isis source-packet-routing]` hierarchy level. All MX and PTX5000 routers with FPC3 onwards support enhanced mode. If enhanced mode is not enabled, configure either the `enhanced-ip` statement or the `enhanced-ethernet` statement at the `[edit chassis network-services]` hierarchy level. On PTX Series routers, configure the `enhanced-mode` statement at the `[edit chassis network-services]` hierarchy level. Note: Currently, MPLS labels correspond only to only one instance, instance 0. Since each SID corresponds to a single `instance_identifier`, no aggregation is required to be done by the collector. The `instance_identifier` is stamped as 0. The following OpenConfig paths are supported: `/network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/in-pkts` `/network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/in-octets` `/network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/out-octets` `/network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/out-pkts` `/network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/in-octets` `/network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/in-pkts` `/network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/out-octets` `/network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/out-pkts` `/network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/in-octets` `/network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/in-pkts` `/network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/out-octets` `/network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/out-pkts` `/network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/in-octets` `/network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/in-pkts` `/network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/out-octets` `/network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/out-pkts`
`/junos/services/segment-routing/sid/usage/`	Sensors for aggregate segment routing traffic with IS-IS. This sensor is supported on PTX3000 routers and PTX5000 routers with FPC2 starting with Junos OS Release 19.1R1. Statistics are exported separately for each routing instance. The first path exports inbound traffic. The second path exports outbound traffic. The third path exports inbound segment routing traffic for each segment identifier. Note: When you enable a sensor for segment routing statistics, you must also configure the `sensor-based-stats` statement at the `[edit protocols isis source-packet-routing]` hierarchy level.
`/junos/services/segment-routing/traffic-engineering/ingress/usage`	Packet Forwarding Engine sensor for ingress segment routing traffic engineering statistics. Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.
`/junos/services/segment-routing/traffic-engineering/transit/usage`	Packet Forwarding Engine sensor for ingress segment routing traffic engineering statistics. Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.
`/junos/services/segment-routing/traffic-engineering/tunnel/lsp/ingress/usage/` `/junos/services/segment-routing/traffic-engineering/tunnel/lsp/transit/usage/`	Sensor for Segment Routing Traffic Engineering (SR-TE) per Label Switched Path (LSP) route statistics. You can stream SR-TE telemetry statistics for uncolored SR-TE policies to an outside collector. Ingress statistics include statistics for all traffic steered by means of an SR-TE LSP. Transit statistics include statistics for traffic to the Binding-SID (BSID) of the SR-TE policy. To enable these statistics, include the `per-source per-segment-list` option at the [`edit protocols source-packet-routing telemetry statistics`] hierarchy level. Starting in Junos OS Release 20.1R1, MX Series and PTX Series routers support streaming statistics using gRPC services. Starting in Junos OS Release 20.2R1, MX240. MX480, MX960, MX2010, and MX2020 with MPC-10E or MPC-11E routers support streaming statistics using gRPC services. When a subscription is made to these resource paths, the following output format is displayed: `/mpls/signaling-protocols/segment-routing/sr-te-per-lsp-ingress-policies/sr-te-ingress-lsp-policy\[tunnel-name='srtelsp1' and source='st' and origin='0' and distinguisher='f' and lsp-name='sr1'\]/state/counters\[name='.'\]/packets` `/mpls/signaling-protocols/segment-routing/sr-te-per-lsp-transit-policies/sr-te-transit-lsp-policy\[tunnel-name='srtelsp1' and source='st' and origin='0' and distinguisher='f' and lsp-name='sr1'\]/state/counters\[name='.'\]/packets` For the output format above, the field `source`, values can be `ST` (static tunnel) or `PC` (PCEP tunnel). For the field `lsp-name`, the value is the transit output. Other fields, such as `Origin` and `Distinguisher` are fixed for uncolored tunnels.
`/system/alarms/alarm`	Sensor for alarms. Starting with Junos OS Release 20.1R1, ON_CHANGE statistics using gNMI services with MX960, MX2020, PTX1000, and PTX5000 routers. These routers support OpenConfig model: openconfig-alarms.yang: oc-ext:openconfig-version 0.3.1
`/system/processes/process/`	Individual Routing Engine core information sensor. You can stream CPU usage statistics per Routing Engine core. Statistics are similar to output from the `show system process detail` operational mode command. This feature supports the private data model openconfig-procmon.yang. Starting in Junos OS Release 20.2R1, streaming statistics using gRPC services or gNMI services on MX960, MX2010, MX2020, PTX1000, PTX5000, and PTX10000 routers QFX5100, and QFX5200 switches is supported.
`/vlans/`	Sensor for VLAN management states. This feature supports OpenConfig model openconfig-vlan.yang configuration version 1.0.2. Starting in Junos OS Release 19.4R1, streaming VLAN statistics using JTI and gRPC services on EX4650 and QFX5120 switches is supported. `/vlans/vlan/state/name` `/vlans/vlan/state/vlan-id` `/vlans/vlan/members/` `/vlans/vlan/members/member/interface-ref/state/interface/` `/vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/interface-mode` `/vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/native-vlan` `/vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/access-vlan` `/vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/trunk-vlan` `/vlans/vlan/members/member/interface-ref/state/interface/vlan/state/vlan-id`

resource path

Description

/junos/system/subscriber-management/aaa/accounting-statistics/

Sensor that tracks accounting statistics by means of a protocol exchange with accounting servers.

You can also add the following to the end path for /junos/system/subscriber-management/aaa/accounting-statistics/:

acct-req-received
acct-req-timeout
acct-resp-failure
acct-resp-success
acct-req-start
acct-req-interim
acct-req-stop
acct-resp-total
acct-resp-start
acct-resp-interim
acct-resp-stop
acct-resp-total

/junos/system/subscriber-management/aaa/address-assignment-statistics/logical-system-routing-instances/logical-system-routing-instance/pools/pool

For Authentication, Authorization, and Accounting, this sensor tracks address pool utilization.

The resource path can be refined to select a logical system routing instance by using a logical system routing instance filter:

/aaa/address-assignment-statistics/logical-system-routing-instances/logical-system-routing-instance [lsri-name=’ lsName:riName’]/pools/pool[pool-name=’ poolName’]

The resource path can be refined to select a specific pool by using a pool filter:

/junos/system/subscriber-management/aaa/address-assignment-statistics/logical-system-routing-instances/logical-system-routing-instance/pools/pool[pool-name=’ poolName’]

The resource path can be refined to select both a logical routing instance and a pool by using a logical system routing instance filter and a pool filter:

/junos/system/subscriber-management/aaa/address-assignment-statistics/logical-system-routing-instances/logical-system-routing-instance/[lsri-name=’ lsName:riName’]/pools/pool[pool-name=’ poolName’]

The following end paths are also supported for the resource path:

pool-name
out-of-memory
out-of-address
address-total
address-in-use
address-usage-percent
linked-pool-name-The next address pool in the chain of linked pools. If there is no next address pool, the value is empty. This leaf is supported in Junos OS Release 18.3R1 and higher.
linked-pool-head-The first address pool in a chain of linked pools. If this pool is not part of a linked address pool, the value is empty. This leaf is supported in Junos OS Release 18.3R1 and higher. For single pools, the value of linked-pool-head should be the same as the pool-name. For example:

key:__prefix__, str_value:/junos/system/subscriber-management/aaa/address-assignment-statistics/logical-system-routing-instances/logical-system-routing-instance[name='default:marberry']/pools/pool[pool-name='john']/}

.
.
kv {
  key:linked-pool-name,
  str_value:jayne
}
kv {
  key:linked-pool-head,
  str_value:john

/junos/system/subscriber-management/aaa/diameter/clients/gx

Sensor for policy and charging rules function (PCRF) statistics for subscribers.

Supported on MX5, MX10, MX40, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, and MX100016 routers for streaming statistics export through gRPC services and gNMI services starting with Junos OS Release 19.3R1.

You can also add the following end paths:

ccr-initial
ccr-initial-retry
cca-initial
cca-initial-grant
cca-initial-deny
cca-initial-failure
ccr-update
ccr-update-retry
cca-update
cca-update-timeout
ccr-terminate
ccr-terminate-retry
cca-terminate
cca-terminate-timeout
cca-parse-error
cca-dropped-no-session-id
cca-dropped-bad-e2e-id
cca-dropped-bad-origin-realm
cca-dropped-bad-origin-host
cca-dropped-no-result-code
cca-dropped-other
cca-initial-bad-result-code
cca-initial-bad-data
rar-update
rar-update-retry
rar-update-drop
raa-update-ack
raa-update-nak-no-session
raa-update-nak-unable-to-comply
raa-update-nak-other
rar-disconnect
rar-disconnect-retry
rar-disconnect-drop
raa-disconnect-ack
raa-disconnect-nak-no-session
raa-update-nak-unable-to-comply
raa-disconnect-nak-other
rar-audit
rar-audit-retry
rar-audit-drop
raa-audit-ack
raa-audit-nak-no-session
raa-audit-nak-unable-to-comply
raa-audit-nak-other

/junos/system/subscriber-management/aaa/diameter/clients/gy

Sensor for Online Charging System (OCS) statistics for subscribers.

You can also add the following end paths:

ccr-initial
ccr-initial-retry
ccr-initial-alternate-retry
cca-initial
cca-initial-alternate
ccr-update
ccr-update-retry
ccr-update-alternate-retry
cca-update
cca-update-alternate
ccr-terminate
ccr-terminate-retry
ccr-terminate-alternate-retry
cca-terminate
cca-terminate-alternate
cca-terminate-timeout
cca-se-error
cca-no-session-id
cca-bad-e2e-id
cca-bad-origin-realm
cca-bad-origin-host
cca-no-result-code
cca-drop
cca-initial-bad-result-code
cca-initial-bad-data
asr
asr-retry
asr-parse-error
asr-update-drop
asa-ack
asa-nak

/junos/system/subscriber-management/aaa/diameter/clients/nasreq

Sensor for Network Access Server Application (NASREQ) statistics for subscribers.

You can also add the following end paths:

authentication-request-messages-sent-Authentication requests successfully sent
authentication-request-message-failures-Authentication requests processing errors
authentication-denies-failures-Authentication requests rejected
authentication-grants-received-Authentication grants received
authorization-request-messages-sent-Authorization requests successfully sent
authorization-request-message-failures-Authorization requests processing errors
authorization-request-messages-timeouts-Authorization requests timed out
authorization-denies-failures-Authorization requests rejected
authorization-grants-received-Authorization grants received
session-terminate-request-messages-sent-Termination requests successfully sent
session-terminate-request-message-failures-Termination requests processing errors
session-terminate-request-messages-timeouts-Termination requests timed out
session-terminate-response-messages-failures-Termination response processing errors
session-terminate-response-messages-received-Termination responses received
abort-session-requests-received-Terminate session requests received
abort-session-response-ack-messages-sent-Terminate session requests responded with ack
abort-session-response-nack-messages-sent-Terminate session requests responded with nack
abort-session-response-message-failures-
transmit-queue-time-outs-Total count of messages dropped from the transmit queue due to timeout
response-parse-errors-Response messages dropped due to parsing errors
responses-dropped-Total count of responses dropped
outstanding-requests-Outstanding request messages

/junos/system/subscriber-management/aaa/diameter/peers/peer[peer_address=’peer-address’]/gx/response-time

Diameter peer sensor that provides response time measurements for messages exchanged between an MX router and the peer for PCRF statistics.

This sensor includes response-time and delay measurements in milliseconds.

Note:

The delay measurements are made over a 60-second measurement interval. As the reporting interval may be as much as 59 seconds out of phase with the measurement interval, the response time values may not be aligned with the reporting interval.

You can also add the following end paths:

1minute_min_resp_time
1minute_avg_resp_time
1minute_max_resp_time
1minute_msgs_sent
1minute_msgs_recvd
1minute_msgs_no_resp

/junos/system/subscriber-management/aaa/diameter/peers/peer[peer_address=’peer-address’]/gy/response-time

Diameter peer sensor that provides response time measurements for messages exchanged between an MX router and the peer for OCS statistics.

This sensor includes response-time and delay measurements in milliseconds.

Note:

You can also add the following end paths:

1minute_min_resp_time
1minute_avg_resp_time
1minute_max_resp_time
1minute_msgs_sent
1minute_msgs_recvd
1minute_msgs_no_resp

/junos/system/subscriber-management/aaa/diameter/peers/peer[peer_address=’peer-address’]/nasreq/response-time

Diameter peer sensor that provides response time measurements for messages exchanged between an MX router and the peer for NASREQ statistics.

This sensor includes response-time and delay measurements in milliseconds.

Note:

You can also add the following end paths:

1minute_min_resp_time
1minute_avg_resp_time
1minute_max_resp_time
1minute_msgs_sent
1minute_msgs_recvd
1minute_msgs_no_resp

/junos/system/subscriber-management/access-network/ancp/adapter

Sensors that track statistics associated with Access Node Control Protocol (ANCP) adapter.

mapped-dynamic-subscriber-count

Number of ANCP subscribers mapped to dynamic interfaces by ANCP adapter.

/junos/system/subscriber-management/access-network/ancp/protocol

Sensors that track statistics associated with ANCP protocol.

`establishing-neighbor-count`	Number of neighbors in the process of establishing adjacency.
`established-neighbor-count`	Number of neighbors in the process of establishing adjacency
`total-neighbor-count`	Total number of neighbors in all states.
`mapped-static-subscriber-count`	Number of ANCP subscribers mapped to static interfaces by ANCP protocol.
`port-up-count`	Total number of port ups received.
`port-down-count`	Total number of port downs received.

/junos/system/subscriber-management/aaa/authentication-statistics/

Sensors that track authentication, authorization, and accounting (AAA) authentication, pre-authentication, and re-authentication statistics.

The following end paths are also supported for the resource path:

req-received
req-accepted
req-rejected
req-challenge
req-timeout
pre-authen-req-received
pre-authen-req-accepted
pre-authen-req-rejected
pre-authen-req-challenge
pre-authen-req-timeout
re-authen-req-received
re-authen-req-accepted
re-authen-req-rejected
re-authen-req-internal-errors
re-authen-req-challenge
re-authen-req_timeout

/junos/system/subscriber-management/aaa/dynamic-request-statistics/

Sensor tracks dynamic request statistics from AAA server-initiated requests, including Change of Authorization (CoA) and RADIUS-initiated Disconnect (RID).

The following end paths are also supported for the resource path:

dynamic-req-received
dynamic-req-success
dynamic-req-error
dynamic-req-silently-drop

/junos/system/subscriber-management/aaa/radius-servers/radius-server/response-time/

Sensor for RADIUS server response time statistics for a specific server.

A request sent to the RADIUS server is counted as a message sent. Similarly, a response to the request is counted as a message received. A timeout during the measurement interval does not impact the minimum, average, or maximum response time statistics, but the event is counted as a no response.

The delay measurements are made over a 60-second measurement interval. The reporting interval can be as much as 59 seconds out of phase with the measurement interval. At reporting time, the values from the last update interval are reported. The response time values are not aligned with the reporting interval.

The resource path can be refined to select a specific RADIUS server by adding a server address filter to the resource path:

/junos/system/subscriber-management//aaa/radius-servers/radius-server[server-address=’radiusIpv4Address’]/response-time/

The following end paths are also supported for the resource path:

one-minute-minimum-response-time
one-minute-average-response-time
one-minute-maximum-response-time
one-minute-messages-sent
one-minute-messages-received
one-minute-messages-no-response

/junos/system/subscriber-management/aaa/radius-servers/radius-server/statistics/

Sensor for RADIUS server statistics for a specific server.

The resource path can be refined to select a specific RADIUS server by adding a server address filter to the resource path:

/junos/system/subscriber-management//aaa/radius-servers/radius-server[server-address=’radiusIpv4Address’]/statistics/

The following end paths are also supported for the resource path:

server-address
server-last-rtt
auth-access-requests
auth-rollover-requests
auth-retransmissions
auth-access-accepts
auth-access-rejects
auth-access-challenges
auth-malformed-responses
auth-bad-authenticators
auth-req-pending
auth-request-timeouts
auth-unknown-responses
auth-packets-dropped
preauth-access-requests
preauth-rollover-requests
preauth-retransmissions
preauth-access-accepts
preauth-access-rejects
preauth-access-challenges
preauth-malformed-responses
preauth-bad-authenticators
preauth-req-pending
preauth-request-timeouts
preauth-unknown-responses
preauth-packets-dropped
acct-start-requests
acct-interim-requests
acct-stop-requests
acct-rollover-requests
acct-retransmissions
acct-start-responses
acct-interim-responses
acct-stop-responses
acct-malformed-responses
acct-bad-authenticators
acct-req-pending
acct-request-timeouts
acct-unknown-responses
acct-packets-dropped

/junos/system/subscriber-management/chassis

/junos/system/subscriber-management/chassis[chassis-index=chassis-index] (to specify an index number for a specific Routing Engine)

Chassis role (backup or primary) sensor.

Starting with Junos OS Release 20.2R1, streaming statistics from a single chassis or virtual chassis is supported using gRPC services with MX480, MX960, MX10003, MX2010, and MX2020 routers.

/junos/system/subscriber-management/chassis/routing-engines/routing-engine]

/junos/system/subscriber-management/chassis/routing-engines/routing-engine[re-index=RoutingEngineIndex] (to specify an index number for a specific Routing Engine)

Routing Engine status and GRES notification sensor.

This sensor provides:

Routing Engine role
Graceful Routing Engine switchover (GRES) readiness state

Starting with Junos OS Release 20.2R1, streaming statistics from a single chassis or virtual chassis is supported using gRPC services with MX480, MX960, MX10003, MX2010, and MX2020 routers.

/junos/system/subscriber-management/chassis/routing-engines/process-status/subscriber-management-processes/subscriber-management-process

/junos/system/subscriber-management/chassis/routing-engines/process-status/subscriber-management-processes/subscriber-management-process[pid=ProcessIdentifier] (to specify a Process ID (PID) for a specific process)

Subscriber management process sensor. This sensor includes leaves per Routing Engine for each running process:

PID
CPU utilization (%)
Process name
Memory utilization (%)

Starting with Junos OS Release 20.2R1, streaming statistics from a single chassis or virtual chassis is supported using gRPC services with MX480, MX960, MX10003, MX2010, and MX2020 routers.

/junos/system/subscriber-management/chassis/routing-engines/routing-engine/dhcp-bindings/dhcp-element[dhcp-type-name=RelayOrServer/v4]

/junos/system/subscriber-management/chassis/routing-engines/routing-engine/dhcp-bindings/dhcp-element[dhcp-type-name=RelayOrServer/v6]

DHCP binding statistics sensor. Statistics for server or relay are streamed per Routing Engine sensor.

The sensor includes statistics on the number of subscribers in the following states:

Initializing
Binding
Bound
Renewing
Restoring
Releasing

Starting with Junos OS Release 20.2R1, streaming statistics from a single chassis or virtual chassis is supported using gRPC services with MX480, MX960, MX10003, MX2010, and MX2020 routers.

/junos/system/subscriber-management/chassis/virtual-chassis-ports/virtual-chassis-port

/junos/system/subscriber-management/chassis/virtual-chassis-ports/virtual-chassis-port[vcp-interface-name=vcp-interface-port-string] (to specify the interface name)

Virtual chassis port counter sensor.

The sensor includes these statistics:

Input packets
Output packets
Input bytes
Output bytes

Starting with Junos OS Release 20.2R1, streaming statistics from a virtual chassis is supported using gRPC services with MX480, MX960, MX10003, MX2010, and MX2020 routers.

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/relay/bindings/

Sensor for DHVPv4 relay binding state statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance name:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[name=’ routing-instance-name]/relay/bindings/

The following end paths are also supported for the resource path:

binding-state-v4relay-binding
binding-state-v4relay-init
binding-state-v4relay-bound
binding-state-v4relay-selecting
binding-state-v4relay-requesting
binding-state-v4relay-renew
binding-state-v4relay-release
binding-state-v4relay-restoring

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/relay/servers/server/response-time

Sensor for DHVPv4 server delay. The sensor periodically measures the minimum, average, and maximum delay or response time from the upstream DHCP server(s), as seen by the relay.

DHCP relay does not track the state of the server. The no-response statistics are the difference between the messages sent and received during the measurement interval.

The delay measurements are made over a 60-second measurement interval. Because the reporting interval can be as much as 59 seconds out of phase with the measurement interval, there is no design to align the response time values with the reporting interval.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[name=’ routing-instance-name]/relay/servers/server/response-time

The resource path can be refined to select a specific DHCP server by adding a server filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/relay/servers/server[server-ip=’ server-ip’]/response-time

The resource path can be refined to select a specific DHCP server in a specific routing instance by adding both a routing instance filter and a server filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[name=’ routing-instance-name]/relay/servers/server[server-ip=’ server-ip’]/response-time

The following end paths are also supported for the resource path:

one-minute-minimum-response-time
one-minute-average-response-time
one-minute-maximum-response-time
one-minute-messages-sent
one-minute-messages-received
one-minute-messages-no-response

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/server/bindings/

Sensor for DHVPv4 server binding state statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[name=’ routing-instance-name]/server/bindings/

The following end paths are also supported for the resource path:

binding-state-v4server-binding
binding-state-v4server-init
binding-state-v4server-bound
binding-state-v4server-selecting
binding-state-v4server-requesting
binding-state-v4server-renew
binding-state-v4server-release
binding-state-server-restoring

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/server/statistics/

Sensor for DHCPv4 telemetry for server statistics for a specific routing-instance.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/server/statistics/

For example, the following resource path defines server statistics for the default:n000015k routing instance: /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ n000015k]/server/statistics

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’] /server/statistics/ the only value supported for routing-instance-name is default.

The following end paths are also supported for the resource path:

dropped-v4server-total
dropped-v4server-bad-hware
dropped-v4server-bootp-pkt
dropped-v4server-bad-bootp-opcode
dropped-v4server-bad-options
dropped-v4server-bad-address
dropped-v4server-no-address
dropped-v4server-no-interface-cfg
dropped-v4server-no-local-address
dropped-v4server-short-pkt
dropped-v4server-no-bad-send
dropped-v4server-no-option60
dropped-v4server-no-option82
dropped-v4server-authentication
dropped-v4server-dynamic-profile
dropped-v4server-no-license
dropped-v4server-no-bad-dhcp-opcode
dropped-v4server-no-options
dropped-v4server-hop-limit
dropped-v4server-ttl-expired
dropped-v4server-bad_udp-checksum
dropped-v4server-inactive-vlan
dropped-v4server-era-start-ailed
dropped-v4server-client-lookup
dropped-v4server-lease-time-violation
offer-delayed
offer-delay-in-progress
offer-delay-total
msg-recv-v4server-boot-request
msg-recv-v4server-decline
msg-recv-v4server-discover
msg-recv-v4server-inform
msg-recv-v4server-release
msg-recv-v4server-request
msg-recv-v4server-renew
msg-recv-v4server-rebind
msg-recv-v4server-lease-query
msg-recv-v4server-bulklease-query
msg-sent-v4server-boot-reply
msg-sent-v4server-offer
msg-sent-v4server-boot-ack
msg-sent-v4server-nak
msg-sent-v4server-force-renew
msg-sent-v4server-unassigned
msg-sent-v4server-unknown
msg-sent-v4server-active
msg-sent-v4server-query-done

/junos/system/subscriber-management/client-protocols/dhcp/v4/

Sensor for DHCPv4 telemetry.

The following end paths are also supported for the resource path:

dropped-total
dropped-bad-read
dropped-ip-header
dropped-short-packet
dropped-no-interface
dropped-no-routing-instance
dropped-no-memory
dropped-recovery-in-progress
era-inflight-count
era-reported-failures
era-reported-successes

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/server/statistics/

Sensor for DHVPv4 server statistics

The resource path can be refined to select a specific routing instance by adding a routing instance name:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/server/statistics/

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-ancpinstance[ri-name=’ routing-instance-name’] /server/statistics/ the only value supported for routing-instance-name is default.

The following end paths are also supported for the resource path:

dropped-v4server-total
dropped-v4server-bad-hware
dropped-v4server-bootp-pkt
dropped-v4server-bad-bootp-opcode
dropped-v4server-bad-options
dropped-v4server-bad-address
dropped-v4server-no-address
dropped-v4server-no-interface-cfg
dropped-v4server-no-local-address
dropped-v4server-short-pkt
dropped-v4server-no-bad-send
dropped-v4server-no-option60
dropped-v4server-no-option82
dropped-v4server-authentication
dropped-v4server-dynamic-profile
dropped-v4server-no-license
dropped-v4server-no-bad-dhcp-opcode
dropped-v4server-no-options
dropped-v4server-hop-limit
dropped-v4server-ttl-expired
dropped-v4server-bad_udp-checksum
dropped-v4server-inactive-vlan
dropped-v4server-era-start-ailed
dropped-v4server-client-lookup
dropped-v4server-lease-time-violation
offer-delayed
offer-delay-in-progress
offer-delay-total
msg-recv-v4server-boot-request
msg-recv-v4server-decline
msg-recv-v4server-discover
msg-recv-v4server-inform
msg-recv-v4server-release
msg-recv-v4server-request
msg-recv-v4server-renew
msg-recv-v4server-rebind
msg-recv-v4server-lease-query
msg-recv-v4server-bulklease-query
msg-sent-v4server-boot-reply
msg-sent-v4server-offer
msg-sent-v4server-boot-ack
msg-sent-v4server-nak
msg-sent-v4server-force-renew
msg-sent-v4server-unassigned
msg-sent-v4server-unknown
msg-sent-v4server-active
msg-sent-v4server-query-done

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/relay/statistics/

Sensor for DHVPv4 relay binding state statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics/

For example, the following resource path defines relay statistics for the default:n000015k routing instance: /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ n000015k]/relay/statistics

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics/ the only value supported for the value routing-instance-name is default.

The following end paths are also supported for the resource path:

dropped-v4relay-total
dropped-v4relay-bad-hardware
dropped-v4relay-bootp-packet
dropped-v4relay-bad-bootp-opcode
dropped-v4relay-bad-options
dropped-v4relay-bad-address
dropped-v4relay-no-address
dropped-v4relay-no-interface-cfg
dropped-v4relay-no-local-address
dropped-v4relay-short-packet
dropped-v4relay-bad-send
dropped-v4relay-option-60
dropped-v4relay-relay-option
dropped-v4relay-option-82
dropped-v4relay-authentication
dropped-v4relay-dynamic-profile
dropped-v4relay-dynamic-profile
dropped-v4relay-license
dropped-v4relay-bad-dhcp-opcode
dropped-v4relay-no-options
dropped-v4relay-hop-limit
dropped-v4relay-ttl-expired
dropped-v4relay-bad-udp-checksum
dropped-v4relay-inactive-vlan
dropped-v4relay-era-start-failed
dropped-v4relay-client-lookup
dropped-v4relay-proxy-no-server-addr
dropped-v4relay-lease-time-violation
dropped-v4relay-leasequery-repl-no-circuitid
dropped-v4relay-leasequery-repl-with-error-code
dropped-v4relay-leasequery-repl-with-query-term
dropped-v4relay-older-leasequery-reply
dropped-v4relay-abort-leasequery-reply-proc
dropped-v4relay-during-leasequery-reply
dropped-v4relay-relay-source-no-lpbk-interface
v4relay-bootp-request-rcvd
msg-recv-v4relay-decline
msg-recv-v4relay-discover
msg-recv-v4relay-inform
msg-recv-v4relay-release
msg-recv-v4relay-request
msg-recv-v4relay-leaseactive
msg-recv-v4relay-leaseunassigned
msg-recv-v4relay-leaseunknown
msg-recv-v4relay-leasequerydone
v4relay-bootp-reply-rcvd
msg-recv-v4relay-offer
msg-recv-v4relay-ack
msg-recv-v4relay-nak
msg-recv-v4relay-forcerenew
v4relay-bootp-reply-sent
msg-sent-v4relay-offer
msg-sent-v4relay-ack
msg-sent-v4relay-nak
msg-sent-v4relay-forcerenew
msg-sent-v4relay-leasequery
msg-sent-v4relay-bulkleasequery
v4relay-bootp-request-sent
msg-sent-v4relay-decline
msg-sent-v4relay-discover
msg-sent-v4relay-inform
msg-sent-v4relay-release
msg-sent-v4relay-request
v4relay-bootp-forwarded-total
v4relay-bootp-request-fwd
v4relay-bootp-reply-fwd

/junos/system/subscriber-management/client-protocols/dhcp/v6/

Sensor for DHCPv6 statistics.

The following end paths are also supported for the resource path:

era-inflight-count
era-reported-failures
era-reported-successes

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/relay/bindings/

Sensor for DHVPv6 relay binding state statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance name:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[name=’ routing-instance-name]/relay/bindings/

The following end paths are also supported for the resource path:

binding-state-v6relay-binding
binding-state-v6relay-init
binding-state-v6relay-bound
binding-state-v6relay-selecting
binding-state-v6relay-requesting
binding-state-v6relay-renew
binding-state-v6relay-release
binding-state-relay-restoring

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/relay/servers/server/response-time

Sensor for DHVPv6 server delay. The sensor periodically measures the minimum, average, and maximum delay or response time from the upstream DHCP server(s), as seen by the relay.

DHCP relay does not track the state of the server. The no-response statistics are the difference between the messages sent and received during the measurement interval.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[name=’ routing-instance-name]/relay/servers/server/response-time

The resource path can be refined to select a specific DHCP server by adding a server address filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/relay/servers/server[server-ip=’ server-ip’]/response-time

The resource path can be refined to select a specific DHCP server in a specific routing instance by adding both a routing instance filter and a server filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[name=’ routing-instance-name]/relay/servers/server [server-ip=’ server-ip’]/response-time

The following end paths are also supported for the resource path:

one-minute-minimum-response-time
one-minute-average-response-time
one-minute-maximum-response-time
one-minute-messages-sent
one-minute-messages-received
one-minute-messages-no-response

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/server/bindings/

Sensor for DHVPv6 binding state statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[name=’ routing-instance-name]/server/bindings/

The following end paths are also supported for the resource path:

binding-state-v6server-binding
binding-state-v6server-init
binding-state-v6server-bound
binding-state-v6server-selecting
binding-state-v6server-requesting
binding-state-v6server-renew
binding-state-v6server-release
binding-state-server-restoring

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/server/statistics/

Sensor for DHCPv6 server statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/server/statistics/

For example, the following resource path defines server statistics for the default:n000015k routing instance: /junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[ri-name=’ n000015k]/server/statistics

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v6/ routing-instances/routing-instance[ri-name=’ routing-instance-name’]/server/statistics the only value supported for routing-instance-name is default.

The following end paths are also supported for the resource path:

dropped-v6server-total
dropped-v6server-no-routing-instance
dropped-v6server-bad-send
dropped-v6server-short-packet
dropped-v6server-bad-msgtype
dropped-v6server-bad-options
dropped-v6server-bad-srcaddress
dropped-v6server-relay-hop-count
dropped-v6server-bad-udp-checksum
dropped-v6server-no-client-id
dropped-v6server-strict-reconfigure
dropped-v6server-option-18
dropped-v6server-authentication{
dropped-v6server-dynamic-profile
dropped-v6server-license
dropped-v6server-inactive-vlan
dropped-v6server-era-start-failed
dropped-v6server-client-lookup
dropped-v6server-lease-time-violation
advertise-delayed
advertise-queued
advertise-total
msg-recv-v6server-dhcpv6-decline
msg-recv-v6server-dhcpv6-solicit
msg-recv-v6server-dhcpv6-information-request
msg-recv-v6server-dhcpv6-release
msg-recv-v6server-dhcpv6-request
msg-recv-v6server-dhcpv6-confirm
msg-recv-v6server-dhcpv6-renew
msg-recv-v6server-dhcpv6-rebind
msg-recv-v6server-dhcpv6-relay-forw
msg-recv-v6server-dhcpv6-leasequery
msg-sent-v6server-advertise
msg-sent-v6server-reply
msg-sent-v6server-logical_nak
msg-sent-v6server-reconfigure
msg-sent-v6server-relay-repl
msg-sent-v6server-leasequery-repl
msg-sent-v6server-leasequery-data
msg-sent-v6server-leasequery-done

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/relay/statistics/

Sensor for DHVPv6 relay statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics/

For example, the following resource path defines relay statistics for the default:n000015k routing instance: /junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[ri-name=’ n000015k]/relay/statistics

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v6/ routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics the only value supported for routing-instance-name is default.

The following end paths are also supported for the resource path:

dropped-v6relay-total
dropped-v6relay-no-safd
dropped-v6relay-no-routing-instance
dropped-v6relay-bad-send
dropped-v6relay-short-packet
dropped-v6relay-bad-msgtype
dropped-v6relay-bad-options
dropped-v6relay-bad-srcaddress
dropped-v6relay-relay-hop-count
dropped-v6relay-bad-udp-checksum
dropped-v6relay-no-client-id
dropped-v6relay-strict-reconfigure
dropped-v6relay-relay-option
dropped-v6relay-option-18
dropped-v6relay-option-37
dropped-v6relay-authentication
dropped-v6relay-dynamic-profile
dropped-v6relay-license
dropped-v6relay-inactive-vlan
dropped-v6relay-era-start-failed
dropped-v6relay-client-lookup
dropped-v6relay-lease-time-violation
dropped-v6relay-leasequery-repl-no-client-data
dropped-v6relay-leasequery-repl-no-interfaceid
dropped-v6relay-leasequery-repl-with-client-link
dropped-v6relay-leasequery-repl-no-relay-data
dropped-v6relay-leasequery-repl-with-hop-cnt
dropped-v6relay-leasequery-repl-with-error-code
dropped-v6relay-leasequery-repl-with-query-term
dropped-v6relay-older-leasequery-reply
dropped-v6relay-abort-leasequery-reply-proc
dropped-v6relay-during-leasequery-reply
dropped-v6relay-relay-source-no-lpbk-interface
msg-recv-v6relay-decline
msg-recv-v6relay-solicit
msg-recv-v6relay-information-request
msg-recv-v6relay-release
msg-recv-v6relay-request
msg-recv-v6relay-confirm
msg-recv-v6relay-renew
msg-recv-v6relay-rebind
msg-recv-v6relay-relay-forw
msg-recv-v6relay-leasequery-repl
msg-recv-v6relay-leasequery-data
msg-recv-v6relay-leasequery-done
msg-recv-v6relay-advertise
msg-recv-v6relay-reply
msg-recv-v6relay-reconfigure
msg-recv-v6relay-relay-repl
msg-recv-v6relay-leasequery
msg-sent-v6relay-reply
msg-sent-v6relay-reconfigure
msg-sent-v6relay-relay-repl
msg-sent-v6relay-leasequery
msg-sent-v6relay-decline
msg-sent-v6relay-solicit
msg-sent-v6relay-information-request
msg-sent-v6relay-release
msg-sent-v6relay-request
msg-sent-v6relay-confirm
msg-sent-v6relay-renew
msg-sent-v6relay-rebind
msg-sent-v6relay-relay-forw
msg-sent-v6relay-leasequery-repl
msg-sent-v6relay-leasequery-data
msg-sent-v6relay-leasequery-done
v6relay-fwd-total
v6relay-fwd-request
v6relay-fwd-reply

/junos/system/subscriber-management/client-protocols/l2tp/summary/

Sensor for L2TP telemetry information.

The following end paths are also supported for the resource path:

l2tp-stats-total-tunnels
l2tp-stats-total-sessions
l2tp-stats-control-rx-packets
l2tp-stats-control-rx-bytes
l2tp-stats-control-tx-packets
l2tp-stats-control-tx-bytes
l2tp-era-type-icrq-inflight-count
l2tp-era-type-icrq-reported-successes
l2tp-era-type-icrq-reported-failures
l2tp-era-type-sccrq-inflight-count
l2tp-era-type-sccrq-reported-successes
l2tp-era-type-sccrq-reported-failures

/junos/system/subscriber-management/client-protocols/ppp/statistics/

Sensors for PPP telemetry information.

The following end paths are also supported for the resource path:

ppp-stats-total-subscriber-sessions
ppp-stats-sessions-disable-phase
ppp-stats-sessions-establish-phase
ppp-stats-sessions-network-phase
ppp-stats-sessions-authenticate-phase

/junos/system/subscriber-management/client-protocols/pppoe/statistics/

Sensors for PPPoE counts.

The following end paths are also supported for the resource path:

padi-packets-sent
padi-packets-received
pado-packets-sent
pado-packets-received
padr-packets-sent
padr-packets-received
pads-packets-sent
pads-packets-received
padt-packets-sent
padt-packets-received
service-error-sent
service-error-received
ac-error-sent
ac-error-received
generic-error-sent
generic-error-received
malformed-packets-received
unknown-packets-received
era-inflight-count
era-reported-successes
era-reported-failures

/junos/system/subscriber_management/dynamic-interfaces/interface-sets/meta-data/interface-set[container-id='container-id-value']/

Sensor for subscriber interface-set information.

This sensor is supported on MX Series routers starting with Junos OS Release 18.4R1.

ON-CHANGE streaming is supported.

The following end paths are supported:

cos-egress-tcp-name-The egress traffic control profile associated with this interface-set.
cos-egress-tcp-remainder-name-The egress remainder traffic control profile associated with this interface-set.
interface-set-name-The name of the interface-set as supplied by AAA or as constructed by the topology relationship (ACI string or interface stacking).
interface-set-type-The type of interface-set (determines structure of interface-set-name).
device-name-The name of the underlying device or port (e.g. ge-1/0/0 or ae1). This leaf is empty if the interface-set-type is not a physical interface-set type.
stag-The outer VLAN tag. The value is 0 if interface-set-type is not a VLAN type.
ctag-The inner VLAN tag. The value is 0 if interface-set-type is not a VLAN type.

/junos/system/subscriber_management/dynamic-interfaces/interface-sets/meta-data/interface[sid-id='sid-value']/

Sensor for subscriber interface information.

ON-CHANGE streaming is supported.

The following end paths are supported:

interface-index-The system assigned interface index for the interface.
session-type-The type of client session (e.g VLAN, DHCP, PPPoE).
user-name-The login name for this interface and session.
profile-name-The name of the client profile used to create the interface.
underlying-interface-name-The name of the associated underlying interface.
cvlan-tag-The innermost VLAN tag value associated with the interface.
svlan-tag-The outermost VLAN tag value associated with the interface.

/junos/system/subscriber_management/dynamic-interfaces/interface-sets/meta-data/interface[sid-id='sid-value']/

Sensor for actual accounting statistics for dynamic subscriber interfaces.

The following end paths are supported:

ip-in-packets-The number of actual transit IPv4 & IPv6 packets received by the interface.
ip-out-packets-The number of actual transit IPv4 & IPv6 packets sent to the interface.
ip-in-bytes-The number of actual transit IPv4 & IPv6 bytes received by the interface.
ip-out-bytes-The number of actual transit IPv4 & IPv6 bytes received by the interface.
ipv6-in-packets-The number of actual transit IPv6 packets received by the interface.
ipv6-out-packets-The number of actual transit IPv6 packets sent to the interface.
ipv6-in-bytes-The number of actual transit IPv6 bytes received by the interface.
ipv6-out-bytes-The number of actual transit IPv6 bytes sent to the interface.

/junos/system/subscriber_management/dynamic-interfaces/interfaces/queue-statistics/interface[sid-id='sid-value']/fpcs/fpc[slot=’slot-value’]/queues/queue/[queue-no=’queue-no-value’]/

Sensor for queue statistics for dynamic interfaces.

The following end paths are supported:

transmitted-packets-The number of actual transit IPv4 & IPv6 packets received by the interface.
transmitted-bytes-Total bytes enqueued for this queue.
dropped-packets-Total packets dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.
dropped-bytes-Total bytes dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.

/junos/system/subscriber_management/dynamic-interfaces/interface-sets/queue-statistics/interface-set[container-id='container-id-value']/fpcs/fpc[slot=’slot-value’]/queues/queue/[queue-no=’queue-no-value’]/

Sensor for queue statistics for dynamic interface-sets.

The following end paths are supported:

transmitted-packets-The number of actual transit IPv4 & IPv6 packets received by the interface.
transmitted-bytes-Total bytes enqueued for this queue.
dropped-packets-Total packets dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.
dropped-bytes-Total bytes dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.

/junos/system/subscriber-management/infra/resource-monitor/chassis

Sensor for chassis resource statistics.

The crossing of chassis thresholds maintained by the resource monitor can be incremented. For each threshold, a count is maintained of rising and falling threshold crossings. As the consumed resource exceeds the threshold, the threshold exceeded count is incremented. As the consumed resource drops below the threshold, the threshold nominal count is incremented.

Unless limits are configured using configured-subscriber-limit, configured and current limit counts will not be visible.

The following end paths are supported for chassis threshold crossing statistics:

subscriber-limit-exceeded
subscriber-limit-nominal
configured-subscriber-limit
current-subscriber-count

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc/statistics/

Sensor for FPC resource statistics, including statistics for throttled sessions due to exceeding the line card load threshold (as measured by the routing engine to FPC round trip delay).

The resource path can be refined to select a specific slot by adding a slot number filter to the resource path:

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc[slot=’ slot number’]/statistics/

Using the slot number filter, the crossing of FPC thresholds maintained by the resource monitor can be incremented. For each threshold, a count is maintained of rising and falling threshold crossings. As the consumed resource exceeds the threshold, the threshold exceeded count is incremented. As the consumed resource drops below the threshold, the threshold nominal count is incremented.

Unless limits are configured using configured-subscriber-limit, configured and current limit counts will not be visible.

The following end paths are supported for FPC threshold crossing statistics:

mem-heap-exceeded
mem-heap-nominal
subscriber-limit-exceeded
subscriber-limit-nominal
configured-subscriber-limit
current-subscriber-count

The following end paths are also supported for the resource path:

heap-memory-used
client-session-denied-count
service-session-denied-count
rtt-throttled-sub-count-client
rtt-throttled-sub-count-client

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc/statistics/pfes/pfe

Sensor for FPC resource statistics at the Packet Forwarding Engine level. Periodically tracks line card statistics and Packet Forwarding Engine statistics.

The resource path can be refined to select a specific Packet Forwarding Engine by adding a Packet forwarding Engine filter to the resource path:

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc/statistics/pfes/pfe[pfe-no=’ pfe number’]/

The resource path can be refined to select a specific Packet Forwarding Engine by adding a slot number filter to the resource path:

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc [slot=’ slot number’]/statistics/pfes/pfe[pfe-no=’ pfe number’]/

Using the slot number filter, the crossing of packet forwarding engine thresholds maintained by the resource monitor can be incremented. For each threshold, a count is maintained of rising and falling threshold crossings. As the consumed resource exceeds the threshold, the threshold exceeded count is incremented. As the consumed resource drops below the threshold, the threshold nominal count is incremented.

The following end paths are supported for packet forwarding threshold crossing statistics:

mem-ifl-exceeded
mem-ifl-nominal
mem-expansion-exceeded
mem-expansion-nominal

The following end paths are also supported for the resource path:

pfe-no
filter-memory-used
ifl-memory-used
expansion-memory-used
nh-memory

/junos/system/subscriber-management/infra/resource-monitor/rsmon-infra/fpcs/fpc[slot=’ slot number’]/

Sensor for FPC resource statistics.

The following end paths are supported for FPC threshold crossing statistics:

delay-round-trip-exceeded
delay-round-trip-nominal

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc [slot=’ slot number’]/statistics/pfes/pfe[pfe-no=’ pfe number’]/sched-blocks/sched-block[sblock-no=’ schedBlockNumber’]/

Sensor for counts of CoS utilization threshold crossing events above (exceeded) and below (nominal).

For each threshold, a count is maintained of rising and falling threshold crossings. As the consumed resource exceeds the threshold, the threshold exceeded count is incremented. As the consumed resource drops below the threshold, the threshold nominal count is incremented.

The following end paths are supported for CoS utilization threshold crossing statistics:

cos-utilization-exceeded
cos-utilization-nominal

The following end paths are supported for statistical data:

queues-max
queues-allocated

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc [slot=’ slot number’]/pics/pic[pic-no=’ pic number’]/

Sensor for PIC threshold crossing.

Unless limits are configured using configured-subscriber-limit, configured and current limit counts will not be visible.

The following end paths are supported for PIC threshold crossing statistics:

subscriber-limit-exceeded
subscriber-limit-nominal
configured-subscriber-limit
current-subscriber-count

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc [slot=’ slot number’]/pics/pic[pic-no=’ pic number’]/ports/port[port-no=’ port number’]/

Sensor for port threshold crossing.

Unless limits are configured using configured-subscriber-limit, configured and current limit counts will not be visible.

The following end paths are supported for port utilization threshold crossing statistics:

subscriber-limit-exceeded
subscriber-limit-nominal
configured-subscriber-limit
current-subscriber-count

/junos/system/subscriber-management/infra/network/dhcp/

Sensor for network stack DHCP. Periodically tracks packets processed by the BBE network stack to and from the DHCP application.

The following end paths are also supported for the resource path:

rx-packet-cnt
era-drops
rx-no-connection
rx-malformed-cnt
rx-no-if-cnt
rx-ifl-invalid
rx-send-failed
tx-packet-cnt
packets-transmitted
tx-malformed-cnt
tx-null-pkt
tx-no-if-cnt
tx-no-iff-cnt
tx-no-rtt-cnt
tx-arp-failed
tx_arp_failed
tx-if-invalid
tx-send-failed
rx-while-not-connected

/junos/system/subscriber-management/infra/network/dvlan/

Sensor for network stack dynamic VLAN. Periodically maintains a count of the number of packets received that triggered dynamic VLAN interface creations.

The following end paths are also supported for the resource path:

rx-packet-cnt

/junos/system/subscriber-management/infra/network/io/

Sensor for network stack IO. Periodcally provides basic network stack input and output and tracks network stack packet statistics.

The following end paths are also supported for the resource path:

l2-rx-packets-cnt
l2-rx-packets-failed
l2-rx-malformed-cnt
l2-rx-ifd-invalid
l2-rx-ifl-invalid
l2-rx-no-iff-cnt
l2-rx-if-create-failed
l2-bbe-io-rcv-l3-unknown-address-family
l2-rx-unsupported-inet-protocol
l2-rx-unsupported-inet6-protocol
l2-rx-unsupported-udp-protocol
l2-rx-unsupported-punt-af
l2-rx-v4-data-path-punt-pkt
l2-rx-v4-data-path-punt-pkt-drop
l2-rx-v6-data-path-punt-pkt
l2-rx-v6-data-path-punt-pkt-drop
l2-tx-packets-cnt
l2-tx-malformed-cnt
l2-tx-no-ifd-cnt
l2-tx-ifl-invalid
l2-bbe-io-send-tx-failed
l2-bbe-io-send-tx-failed-partial
l2-tx-v4-out-error-local-intf
l2-tx-v6-out-error-local-intf
l3-rx-packet-cnt
l3-rx-unsupported-protocol
l3-tx-packet-cnt
l3-tx-send-failed
l3-tx-v4-kernel-forward
l3-tx-v4-kernel-forward-drops
l3-tx-v6-kernel-forward
l3-tx-v6-kernel-forward-drops

/junos/system/subscriber-management/infra/network/dvlan/

Sensor for network stack dynamic VLAN. Periodically maintains a count of the number of packets received that triggered dynamic VLAN interface creations.

The following end paths are also supported for the resource path:

rx-packet-cnt

/junos/system/subscriber-management/infra/network/l2tp/

Sensor network stack L2TP. Periodically tracks L2TP packets processed by the BBE network stack to and from the L2TP application.

The following end paths are also supported for the resource path:

rx-cnt
rx-pkt-cnt
ppp-rx-pkt-cnt
tx-pkt-cnt
ppp-rx-lcp-conf-req-count
ppp-rx-lcp-conf-ack-count
ppp-rx-lcp-conf-nack-count
ppp-rx-lcp-term-req-count
ppp-rx-lcp-term-ack-count
ppp-rx-lcp-echo-req-count
ppp-rx-lcp-echo-resp-count
ppp-rx-pap-req-count
ppp-rx-pap-ack-count
ppp-rx-pap-nack-count
ppp-rx-chap-challenge-count
ppp-rx-chap-resp-count
ppp-rx-chap-success-count
ppp-rx-chap-fail-count
ppp-rx-ipcp-conf-req-count
ppp-rx-ipcp-conf-ack-count
ppp-rx-ipcp-conf-nack-count
rx-malformed-cnt
ppp-rx-unknown-protocol
rx-msg-cnt
rx-msg-processd-cnt
rx-msg-err
rx-invalid-msg-cnt
tx-cnt
ppp-tx-lcp-conf-req-count
ppp-tx-lcp-conf-ack-count
ppp-tx-lcp-conf-nack-count
ppp-tx-lcp-echo-req-count
ppp-tx-lcp-echo-resp-count
ppp-tx-lcp-term-req-count
ppp-tx-lcp-term-ack-count
ppp-tx-pap-req-count
ppp-tx-pap-ack-count
ppp-tx-pap-nack-count
ppp-tx-chap-challenge-count
ppp-tx-chap-resp-count
ppp-tx-chap-success-count
ppp-tx-chap-fail-count
ppp-tx-ipcp-conf-req-count
ppp-tx-ipcp-conf-ack-count
ppp-tx-ipcp-conf-nack-count
ppp-tx-unknown-protocol
tx-pkt-send-failed
tx-pkt-err
tx-msg-cnt
tx-msg-err

/junos/system/subscriber-management/infra/network/ppp/

Sensor network stack PPP. Periodically tracks PPP packets processed by the BBE network stack to and from the PPP application.

The following end paths are also supported for the resource path:

rx-network-pkt-cnt
rx-plugin-pkt-cnt
rx-lcp-conf-req-cnt
rx-lcp-conf-ack-cnt
rx-lcp-conf-nack-cnt
rx-lcp-conf-rej-cnt
rx-lcp-term-req-cnt
rx-lcp-term-ack-cnt
rx-lcp-code-rej-cnt
rx-lcp-protocol-rej-cnt
rx-lcp-echo-req-cnt
rx-lcp-echo-reply-cnt
rx-pap-req-cnt
rx-pap-ack-cnt
rx-pap-nack-cnt
rx-chap-challenge-cnt
rx-chap-resp-cnt
rx-chap-success-cnt
rx-chap-failure-cnt
rx-ipcp-req-cnt
rx-ipcp-ack-cnt
rx-ipcp-nack-cnt
rx-ipv6cp-req-cnt
rx-ipv6cp-ack-cnt
rx-ipv6cp-nack-cnt
rx-malformed-cnt
rx-no-if-cnt
rx-unsupported
tx-cnt
tx-lcp-conf-req-cnt
tx-lcp-conf-ack-cnt
tx-lcp-conf-nack-cnt
tx-lcp-echo-req-cnt
tx-lcp-echo-reply-cnt
tx-lcp-term-req-cnt
tx-lcp-term-ack-cnt
tx-pap-req-cnt
tx-pap-ack-cnt
tx-pap-nack-cnt
tx-chap-challenge-cnt
tx-chap-resp-cnt
tx-chap-success-cnt
tx-chap-failure-cnt
tx-ipcp-req-cnt
tx-ipcp-ack-cnt
tx-ipcp-nack-cnt
tx-ipv6cp-req-cnt
tx-ipv6cp-ack-cnt
tx-ipv6cp-nack-cnt
tx-unknown-pkt-cnt
tx-send-failed
tx-malformed-cnt

/junos/system/subscriber-management/infra/network/pppoe/

Sensor for network stack PPPoE statistics. PPPoE packets processed by the BBE network stack to and from the PPPoE application are tracked.

The following end paths are also supported for the resource path:

rx-cnt
rx-padi-cnt
rx-padr-cnt
rx-ppp-cnt
rx-malformed-cnt
rx-no-if-cnt
rx-unsupported
rx-padi-era-discards
tx-cnt
tx-send-failed

/junos/system/subscriber-management/infra/sdb/statistics/client-type/

Sensor for session database resources session counts by client type.

The following end paths are also supported for the resource path:

dhcp-client-count
vlan-client-count
ppp-client-count
pppoe-client-count
l2tp-client-count
static-client-count
vpls-pw-client-count
mlppp-client-count
essm-client-count
total-client-count

/junos/system/subscriber-management/infra/sdb/statistics/state/

Sensor for session database resources tracking session counts by state.

The following end paths are also supported for the resource path:

init-state-count
configured-state-count
active-state-count
terminating-state-count
terminated-state-count
total-state-count

/junos/system/linecard/ddos/

This PFE sensor exports the statistics of DDOS from MPC1, MPC2, MPC3, MPC5, MPC6, MPC7, MPC8, and MPC9 line cards.

Release History Table

Release

Description

20.3R1

Starting with Junos OS Release 20.3R1, gRPC service for exporting LDP and mLDP statistics is supported on MPC10E-10C-MRATE, MPC10E-15C-MRATE, and MX2K-MPC11E line cards.

20.2R1

Starting with Junos OS Evolved Release 20.2R1, gRPC service for streaming NDP statistics is supported on PTX10001 routers.

20.2R1

Starting with Junos OS Release 20.2R1, gRPC service for streaming Packet forwarding Engine and Routing Engine statistics is supported on EX2300, EX2300-MP, and EX3400 switches.

20.2R1

Starting with Junos OS Release 20.2R1, streaming BGP global, peer and perr groups statistics using gRPC services is supported on EX2300, EX3400, EX4300, EX4600, and EX9200 switches.

20.2R1

Starting with Junos OS Release 20.2R1 sensors to stream standby Routing Engine statistics are supported on MX480, MX960, MX10003, MX2010, and MX2020 routers.

20.2R1

Starting with Junos OS Release 20.2R1, gRPC service for exporting LDP and mLDP statistics is supported on MX Series routers.

20.1R1

Starting with Junos Release 20.R1, gNMI service for streaming telemetry sensors for Packet Forwarding Engine statistics is supported on MX2K-MPC11E line cards on MX2010 and MX2020 routers.

19.4R1

Starting with Junos OS Release 19.4R1, gRPC service for streaming Packet Forwarding Engine and Routing Engine statistics is supported on EX4300-MP switches.

19.3R1

Starting with Junos OS Release 19.3R1, gNMI services for streaming Packet Forwarding Engine statistics is supported on MX240, MX480 and MX960 routers.

19.3R1

Starting with Junos OS Evolved Release 19.3R1, gRPC service for exporting statistics is supported on QFX5220-128C and QFX5220-32CD switches.

19.2R1

Starting with Junos OS Release 19.2R1, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800, and vSRX Series Services Gateways.are supported.

19.2R1

Starting with Junos OS Release 19.2R1, gNMI services for streaming statistics is supported on QFX5110, QFX5120, QFX5200 and QFX5210 switches.

19.2R1

Starting with Junos OS Release 19.3R1, gNMI services for streaming and ON_CHANGE export of Routing Engine statistics is supported on MX960, MX2010, MX2020, PTX5000, PTX1000, and PTX10000 routers.

19.1R1 EVO

19.1R1

Starting with Junos OS Evolved 19.1R1, Packet Forwarding Engine sensors on PTX10003 routers are also supported.

18.4R1

Starting with Junos OS Release 18.4R1, MX480, MX960, MX2010, MX2020, MX2008 and MX-ELM routers are also supported.

18.3R1

Starting with Junos OS Release 18.3R1, ON_CHANGE streaming of LLDP telemetry sensor information is supported through gRPC for MX Series and PTX Series routers.

18.3R1

Starting with Junos OS Release 18.3R1, QFX5120-AY and EX4650 switches are also supported.

18.3R1

Starting with Junos OS Release 18.4R1, EX4600 switches are also supported.

18.2R1

Starting with Junos OS Release 18.2R1, PTX10002 routers are also supported.

18.1R1

Starting with Junos OS Release 18.1R1, QFX5210-64C switches and QFX5100 switches are also supported.

18.1R1

Starting with Junos OS Release 18.1R1, ON_CHANGE streaming of ARP, ND, and IP sensor information associated with interfaces is supported through gRPC for MX Series routers and PTX Series routers.

17.4R1

Starting with Junos OS Release 17.4R1, PTX10016 routers and virtual MX Series (vMX) routers are also supported.

17.3R1

Starting with Junos OS Release 17.3R1, QFX5110 switches, EX4600, EX4600-VC, and EX9200 switches and the Routing and Control Board (RCB) on PTX3000 routers are also supported.

17.3R1

Starting with Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensors are supported.

17.3R1

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’] /server/statistics/ the only value supported for routing-instance-name is default.

17.3R1

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-ancpinstance[ri-name=’ routing-instance-name’] /server/statistics/ the only value supported for routing-instance-name is default.

17.3R1

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics/ the only value supported for the value routing-instance-name is default.

17.3R1

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v6/ routing-instances/routing-instance[ri-name=’ routing-instance-name’]/server/statistics the only value supported for routing-instance-name is default.

17.3R1

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v6/ routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics the only value supported for routing-instance-name is default.

17.2R1

Starting with JunosOS Release 17.2R1, QFX10002, QFX10008, and QFX10016 switches, QFX5200 switches, and PTX1000 and PTX10008 routers are also supported.

16.1R3

Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface)

Supported gRPC and gNMI Sensors

Related Documentation