-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Prometheus Exporter: Problem when scraping metrics from multiple targets that emits metrics of the same name and labelkeys #1076
Comments
I have a branch with a repro here. It switches between showing This must happen somewhere after the receiver as @jhengy was seeing this issue using the Prometheus receiver and the demo uses the OC receiver. This seems like a pretty critical bug? |
Speculative fix orijtech/prometheus-go-metrics-exporter#10 |
It seems like a possible workaround for this situation is to add distinct dummy labels to metrics emitted by different targets to differentiate between them. After I made this commit, we see that otel-collector can export identically named metrics from both generators.
|
This issue is still not resolved and is reproducible with latest version. |
@arpitjindal97 the issue in the Prometheus Exporter was fixed by #1096. |
…y#1076) Bumps [boto3](https://github.com/boto/boto3) from 1.20.26 to 1.20.28. - [Release notes](https://github.com/boto/boto3/releases) - [Changelog](https://github.com/boto/boto3/blob/develop/CHANGELOG.rst) - [Commits](boto/boto3@1.20.26...1.20.28) --- updated-dependencies: - dependency-name: boto3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Describe the bug
if otel-collector/agent scrapes from two endpoints which emits metrics of the same name(even with different label), it seems to only export metrics from one of the endpoints in a random fashion.
Steps to reproduce
metrics-load-generator2
which emits exactly the same metrics asmetrics-load-generator
except thesource
labelcd exaples/demo
docker-compose up
curl localhost:8889/metrics
What did you expect to see?
Will see metrics from both metrics-load-generator(source=source1) and metrics-load-generator2( source=source2)
What did you see instead?
At anytime, only see metrics from one of the sources.
Sometimes seeing this (only observe metrics from the metrics-load-generator service):
sometimes seeing this(only see metrics from the metrics-load-generator2 service):
What version did you use?
Version:
otel/opentelemetry-collector-dev:ffd2a1eb98980702fd642d8a9e4c270934e82e67
What config did you use?
Config: (e.g. the yaml config file)
Environment
OS: Ubuntu 18.04
The text was updated successfully, but these errors were encountered: