Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Junos Telemetry Interface


For Routing Engine telemetry sensors supported by this platform, see Telemetry Sensor Explorer. If any Platform Forwarding Engine sensors have been added for this release, they are listed below

  • End-of-message notification for Routing Engine sensors (EX2300, EX4300, EX4300-MP, EX9200, MX240, MX960, MX10016, MX2010, MX2020, PTX1000, PTX3000, PTX10001, QFX5100, QFX5110, QFX5120, and QFX10002)—Starting in Junos OS Release 21.2R1, we've introduced an end-of-message (EoM) Boolean flag for all Junos telemetry interface (JTI) Routing Engine sensors. The flag notifies the collector that the current wrap has completed for a particular sensor path. A wrap is a complete key-value data dump for all the leaves under a sensor path.

    The EoM flag also enables the collector to detect when the end of wrap occurs without having to compare stream creation timestamp values that the collector receives from the packets. Comparing timestamp values is costly time-wise and delays data aggregation.

    To use this feature with gRPC Network Management Interface (gNMI) transport or Remote Procedure Call (gRPC), retrieve the protobuf files from the relevant branch on the Juniper Networks download site:

    • GnmiJuniperTelemetryHeaderExtension.proto (gNMI)
    • agent.proto (for gRPC)

    For example:

    After you download and install the new protobuf files on a collector, the EoM field is present in the packets received.

    [See Understanding OpenConfig and gRPC on Junos Telemetry Interface.]

  • CoS sensor support (MX204, MX240, MX960, MX2010, MX2020, MX10003, MX10008, MX10016, MX-ELM and vMX)

    Starting in Junos OS Release 21.2R1, we support the following streaming sensors with Junos telemetry interface (JTI).

    • Interface queue extended statistics Packet Forwarding Engine sensors supported with Remote Procedure Call (gRPC): /interfaces/interface/state/counters/out-queue/lp-red-drop-pkts, /interfaces/interface/state/counters/out-queue/hp-red-drop-pkts, /interfaces/interface/state/counters/out-queue/queued-pkts, and /interfaces/interface/state/counters/out-queue/queued-bytes.
    • CoS interface set description Routing Engine sensor supported with gRPC: /qos/interfaces/interface/state/interface-id.
    • Forwarding class to queue mapping Routing Engine sensors supported with gRPC: /qos/forwarding-groups/forwarding-group/state/name and /qos/forwarding-groups/forwarding-group/state/output-queue.
    • Interface extended statistics sensor with native (UDP) support: /junos/system/linecard/interface/queue/extended-stats/.

    [See sensor (Junos Telemetry Interface) and Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface)].

  • JTI: logical interface statistics for IPv4 and IPv6 family input and output counters (MX Series and PTX Series routers using third-generation FPCs)—Starting in Junos OS Release 21.2R1, you can stream per-family logical interface statistics for IPv4 and IPv6 traffic using Junos telemetry interface (JTI) and Remote Procedure Calls (gRPC) to an outside collector.

    To access these sensors, use the resource paths /junos/system/linecard/interface/logical/family/ipv4/usage/ and /junos/system/linecard/interface/logical/family/ipv6/usage/ in a subscription.

    [See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]