-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
OpenTelemetry Collector Prometheus exporter fails with "was collected before with the same name and label values" #33310
Comments
Pinging code owners for exporter/prometheus: @Aneurysm9. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Related: #24054 |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
Open Telemetry Collector prometheus exporter
Describe the issue you're reporting
Hi All,
I have a java service deployed in k8s with a opentelemetry collector attached as sidecar to export the metrics from the application.
I have configured prometheus to scrape the pod via a ServiceMonitor in the same namespace.
All seems to be good , but when I look in the logs I see the following error.
"metric XXX was collected before with the same name and label values"
I tried almost everything but nothing seems to fix it. From the error it seems that I have an exact same metrics that was collected before and because of that its failing do collect it again.
Any idea where I can look ? maybe at prometheus side somewhere ? Or is there a way I can instruct Prometheus to ignore this duplicate and just go fwd with the scrape ?
Thanks for the help
Mircea
The text was updated successfully, but these errors were encountered: