Does On Box aggregation support available for the sensor path /network-instances/network-instance/segment-routing/traffic-engineering/tunnel/usage/
Observing the multiple copies from the same subscription path
In a router when there are more than one FPC present, subscribing to the path /network-instances/network-instance/segment-routing/traffic-engineering/tunnel/usage/ produces the subscription data from multiple producers. The producers for the sensor path is FPC.
Please refer the below example with the explanation:
<-- There are two FPC's on the device. user@r0-RE0-re0> show chassis fpc Temp CPU Utilization (%) CPU Utilization (%) Memory Utilization (%) Slot State (C) Total Interrupt 1min 5min 15min DRAM (MB) Heap Buffer 0 Online 0 4 4 3 3 3 16384 37 1 1 Online 0 3 4 3 3 3 16384 27 1 <-- Subscribed to the path /network-instances/network-instance/segment-routing/traffic-engineering/tunnel/usage/ regress@r0-RE0-re0> show agent sensors Sensor Information : Name : sensor_1000 Resource : /network-instances/network-instance/segment-routing/traffic-engineering/tunnel/usage/ Version : 1.0 Sensor-id : 562949953421314 Subscription-ID : 1000 Component(s) : fpc0/evoaft-jvisiond-bt,fpc1/evoaft-jvisiond-bt Profile Information : Name : export_1000 Reporting-interval : 10 Payload-size : 5000 Address : 0.0.0.0 Port : 1000 Timestamp : ntp Format : GPB <-- There are two producers, namely fpc0/evoaft-jvisiond-bt and fpc1/evoaft-jvisiond-bt <-- The collector receives the following subscription data from both the producers. <-- Each producer will be identified by component-id field <-- Each component-id will be identified by the following notion: component_id: 0 = FPC-X component_id: 1 = FPC-Y system_id: r0-RE0 component_id: 1 <<<<<<< produced by the FPC-1 sub_component_id: 0 path: sensor_1000_1_1:/network-instances/network-instance/segment-routing/traffic-engineering/tunnel/usage/:/network-instances/network-instance/segment-routing/traffic-engineering/tunnel/usage/:evo-aftmand-bt sequence_number: 1072 timestamp: 1717538709678 sync_response: false key: __timestamp__ uint_value: 1717538709679 key: __junos_re_stream_creation_timestamp__ uint_value: 1717538709677 key: __junos_re_payload_get_timestamp__ uint_value: 1717538709677 key: __prefix__ str_value: /network-instances/network-instance[name='master']/segment-routing/te-policies/te-policy[endpoint='::' and color='12035']/ key: state/counters/in-pkts uint_value: 0 key: state/counters/in-octets uint_value: 0 key: __prefix__ system_id: r0-RE0 component_id: 0 <<<< produced by FPC-0 sub_component_id: 0 path: sensor_1000_1_1:/network-instances/network-instance/segment-routing/traffic-engineering/tunnel/usage/:/network-instances/network-instance/segment-routing/traffic-engineering/tunnel/usage/:evo-aftmand-bt sequence_number: 1072 timestamp: 1717538709680 sync_response: false key: __timestamp__ uint_value: 1717538709681 key: __junos_re_stream_creation_timestamp__ uint_value: 1717538709677 key: __junos_re_payload_get_timestamp__ uint_value: 1717538709677 key: __prefix__ str_value: /network-instances/network-instance[name='master']/segment-routing/te-policies/te-policy[endpoint='::' and color='12035']/ key: state/counters/in-pkts uint_value: 41005 key: state/counters/in-octets uint_value: 4592560 <-- As noticed above, with multiple producers in the router, the subscription path stats are not aggregated on the box, rather they are streamed per producer. <-- The collector should aggregate the stats based on the component-id and subscription path.