In CRA-FRR we enabled interface metrics by including prometheus-node-exporter. However with CRA-vSR no such mechanism exist as of today.
Metrics that should be included per interface:
-
node_network_speed_bytes
-
node_network_receive_packets_total
-
node_network_receive_bytes_total
-
node_network_receive_drop_total
-
node_network_receive_errs_total
-
node_network_transmit_packets_total
-
node_network_transmit_bytes_total
-
node_network_transmit_drop_total
-
node_network_transmit_errs_total
-
node_network_up
-
node_network_carrier_changes_total
-
node_network_carrier_down_changes_total
-
node_network_carrier_up_changes_total
The metrics do not need to have the same name as the ones from node-exporter. Something like nwop_vsr_intf_speed_bytes is also fine.
If device is hardware interface (and possible): Include SFP metrics (optical levels, transceiver info etc) from ethtool -m <intf>, especially laser output and receive power for each lane (if multiple lanes are present, e.g. for QSFP links).
In CRA-FRR we enabled interface metrics by including prometheus-node-exporter. However with CRA-vSR no such mechanism exist as of today.
Metrics that should be included per interface:
node_network_speed_bytesnode_network_receive_packets_totalnode_network_receive_bytes_totalnode_network_receive_drop_totalnode_network_receive_errs_totalnode_network_transmit_packets_totalnode_network_transmit_bytes_totalnode_network_transmit_drop_totalnode_network_transmit_errs_totalnode_network_upnode_network_carrier_changes_totalnode_network_carrier_down_changes_totalnode_network_carrier_up_changes_totalThe metrics do not need to have the same name as the ones from node-exporter. Something like
nwop_vsr_intf_speed_bytesis also fine.If device is hardware interface (and possible): Include SFP metrics (optical levels, transceiver info etc) from
ethtool -m <intf>, especially laser output and receive power for each lane (if multiple lanes are present, e.g. for QSFP links).