In EOS 4.25.2F-EFT1 ocprometheus can throw something similar when subscribing to openconfig paths via gnmi/OCTA:
collected metric "intfCounter" { label:<name:"countertype" value:"out-unicast-pkts" > label:<name:"intf" value:"Management1" > gauge:<value:1.84297e+06 > } was collected before with the same name and label values
This is due to nil prefix in the openconfig notif which can cause ocprometheus to complain about having handled a metric already
In EOS 4.25.2F-EFT1 ocprometheus can throw something similar when subscribing to openconfig paths via gnmi/OCTA:
This is due to nil prefix in the openconfig notif which can cause ocprometheus to complain about having handled a metric already