Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error "*** was collected before with the same name and label values" #68

Open
marcolan018 opened this issue Feb 13, 2019 · 4 comments · May be fixed by #78
Open

error "*** was collected before with the same name and label values" #68

marcolan018 opened this issue Feb 13, 2019 · 4 comments · May be fixed by #78

Comments

@marcolan018
Copy link

An error has occurred during metrics collection:

300 error(s) occurred:
* collected metric collectd_PCHMonitor__User_BSOS1_SweepFramework_SweepQueue_AbandonedContentDeletionSweep_gauge gauge:<value:0 >  was collected before with the same name and label values
* collected metric collectd_PCHMonitor__CPU_gauge gauge:<value:150 >  was collected before with the same name and label values

When using collectd exporter v0.4.0, we run into above error. By searching in google, seems this error is due to duplicate metrics. We are aware the best option to resolve this problem is to remove the duplicate ones. But compared with this, with similar configuration, the metrics works well for Graphite Writer. Seems that means this exporter is not flexible enough.

We found a possible workaround here: prometheus/node_exporter#377 (comment). Not sure whether collectd exporter support this.

@josephlim75
Copy link

Hey bluezoe,

Do you get any solution for this duplicate metrics issue in collectd exporter ?

@hoesler hoesler linked a pull request Jun 28, 2019 that will close this issue
@ainiml
Copy link

ainiml commented Aug 22, 2020

getting the same problem

* collected metric "atNetAddress" { label:<name:"atIfIndex" value:"58" > label:<name:"atNetAddress" value:"1.10.254.254" > gauge:<value:1 > } was collected before with the same name and label values

@eero-t
Copy link

eero-t commented Jan 3, 2024

@octo is this related to #78 ?

@octo
Copy link
Contributor

octo commented Jan 3, 2024

This does sound like a duplicate metric. There is a small chance this is caused by the name mangling mapping to distinct collectd metrics to one Prometheus metric. In my experience it is much more likely that there are legitimately two metrics with the same identity, as the file system metrics mentioned by OP.

#78 is talking about a different issue, where there is a mismatch in the number of values/data sources expected and present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants