-
Notifications
You must be signed in to change notification settings - Fork 1.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
[processor/batch] processor ID missing from the metadata_cardinality metric #9674
Labels
bug
Something isn't working
Comments
It happens in v0.99.0 still. |
Came across this bug as I was making the change #10233. The measurement for this metric doesn't add the attributes that other metrics do |
codeboten
added a commit
to codeboten/opentelemetry-collector
that referenced
this issue
May 28, 2024
Fixing this bug required a change in mdatagen to ensure attributes could be passed in to the telemetry builder. Fixes open-telemetry#9674 Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
Submitted a fix for this in #10245 |
codeboten
added a commit
to codeboten/opentelemetry-collector
that referenced
this issue
May 28, 2024
Fixing this bug required a change in mdatagen to ensure attributes could be passed in to the telemetry builder. Fixes open-telemetry#9674 Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
codeboten
added a commit
that referenced
this issue
May 29, 2024
Fixing this bug required a change in mdatagen to ensure attributes could be passed in to the telemetry builder. Fixes #9674 --------- Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
steves-canva
pushed a commit
to Canva/opentelemetry-collector
that referenced
this issue
Jun 14, 2024
…elemetry#10245) Fixing this bug required a change in mdatagen to ensure attributes could be passed in to the telemetry builder. Fixes open-telemetry#9674 --------- Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When having more than one batchers, for example:
The metric is like:
It's not clear which value it is.
What did you expect to see?
I want to have the
processor
label in the metric, and display them in two lines:From the code, https://github.com/open-telemetry/opentelemetry-collector/blob/main/processor/batchprocessor/metrics.go#L97
It can take the value from either processor.
What version did you use?
v0.95.0
The text was updated successfully, but these errors were encountered: