Enhancements to BGP peer sensors for Junos Telemetry Interface

Telemetry data streamed through gRPC for BGP peers is reported separately for each routing instance. To export data for BGP peers, you must now include the following path in front of all supported paths:  /network-instances/network-instance/[name_'instance-name']/protocols/protocol/ 

Additionally, the following paths are also now 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/snmp-peer-index 
•  /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/neighbor/state/ImportEval 
•  /network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/state/ImportEvalPending

 Use the telemetrySubscribe RPC to specify telemetry parameters and provision the sensor. If your device is running a version of Junos OS with an upgraded FreeBSD kernel, you must download the Junos Network Agent software package, which provides the interfaces to manage gRPC subscriptions.