Expanded physical interface queue and traffic statistics sensors for Junos Telemetry Interface (JTI)

Junos OS supports additional resource paths are added to stream physical (IFD) statistics. 

Both traffic and queue statistics for physical interfaces (IFD) are sent out together using the resource path /interfaces for gRPC streaming (which is internally used to create /junos/system/linecard/interface/) or /junos/system/linecard/interface/ for UDP (native) sensors. 

Now, traffic and queue statistics can be delivered separately. Doing so can reduce the reap time for non-queue data for platforms supporting Virtual Output Queues (VOQ). 

The following UDP resource paths can be configured: 

•  /junos/system/linecard/interface/ is the existing resource path (no change). Traffic and queue statistics are sent together. 
• /junos/system/linecard/interface/traffic/ exports all fields except queue statistics. 
•  /junos/system/linecard/interface/queue/ exports queue statistics. 

The gRPC resource path /interfaces now has the following behavior: 

•  It delivers all IFD traffic and queue statistics and delivers statistics in two sensors: 
•  /junos/system/linecard/interface/traffic/ exports all fields except queue statistics. 
•  /junos/system/linecard/interface/queue/ exports queue statistics. 

To provision the sensor to export data through gRPC, use the telemetrySubcribe RPC to specify telemetry parameters. For streaming through UDP, all parameters are configured at the [edit services analytics] hierarchy level. Streaming telemetry data through gRPC also requires the OpenConfig for Junos OS module. OpenConfig and Network Agent packages are bundled into the Junos OS image by default. Both packages support the Junos Telemetry Interface (JTI). 

For exporting statistics using UDP native sensors, configure parameters at the [edit services analytics] hierarchy level.