#Duplicate metric key

1 messages · Page 1 of 1 (latest)

graceful rose
#

I am seeing these errors within the logs of harvest on one of our clusters.

{"level":"error","Poller":"node03","collector":"Zapi:Volume","error":"duplicate metric key => volume-attributes.volume-space-attributes.size-available","key":"volume-attributes.volume-space-attributes.size-available","display":"size_available","caller":"collector/parsers.go:123","time":"2024-02-15T15:07:40-08:00","message":"Failed to add metric"}

{"level":"error","Poller":"node03","collector":"Zapi:Aggregate","error":"duplicate metric key => aggr-attributes.aggr-space-attributes.percent-used-capacity","key":"aggr-attributes.aggr-space-attributes.percent-used-capacity","display":"space_used_percent","caller":"collector/parsers.go:123","time":"2024-02-15T15:07:39-08:00","message":"Failed to add metric"}

I am unsure what is causing these and whether I should be concerned about them or debug further. I feel like this is likely leaving some data out, but there isn't enough information about the 'key' that is causing it.

#

I don't see this on any other cluster we have (I searched all the other logs)

ionic ridge
#

@graceful rose

  1. Have there been any modifications to the Zapi Collector's volume.yaml and aggr.yaml templates?
  2. To rule out any functional issues, could you verify if you are getting volume_size_available and aggr_space_used_percent metrics for these clusters?
  3. Could you share your logs with us? You can send them to ng-harvest-files@netapp.com. You can refer to our log collection guide at https://netapp.github.io/harvest/23.11/help/log-collection
graceful rose
#

Is there a way to find out which key it's saying is a duplicate? I am not sure I have seen any documentation on how to find that out with the poller...

graceful rose
#

well, it looks like there was an issue with one of our cluster nodes that presented itself as having this issue. I am not sure I understand WHY other than the BSD queue limit was being reached, causing this to present like this.

#

crossing fingers that was the cause, since I did the failover/giveback, this has not re-occurred

ionic ridge
#

It's good to know that the problem has not occurred again. But, it should be independent of the issue you are mentioning. This error seems to have occurred during template parsing itself. The error indicates that the metrics volume_size_available and aggr_space_used_percent are defined twice in the Zapi Aggregate template.

graceful rose
#

This was the error that I was receiving....