Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Fix view bugs where views create conflicting metric streams at runtime #3129
Fix view bugs where views create conflicting metric streams at runtime #3129
Changes from 9 commits
19f4443
521fc6d
1688884
866535e
b15fb65
e90644d
403e572
ee7ab4c
cfee469
b44cb72
363b98a
3bf47f8
2d47c2d
462d1af
d8efbce
7a9a450
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we still need this check, and warning, for the following test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This log must only be inside the if (metrics.Count==0) part.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On second thought, I removed this log message. I think it is unnecessary. It is not an issue of a duplicate conflicting metric instrument. The
if (metrics.Count == 0)
case is meant to handle instruments mapping to identical metric streams (i.e., same name, kind, description, etc) - so it is safe to aggregate together.For example, this test covers this case
opentelemetry-dotnet/test/OpenTelemetry.Tests/Metrics/MetricAPITest.cs
Lines 503 to 524 in 3bf47f8
Both
instrument1
andinstrument2
match the first view, the metric stream is identical, so they can be aggregated together. The second view is ignored, and a log message is produced in this case.Update: Actually this log message does still belong. I incorrectly moved it. Moved it back per your comment here #3129 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved and added a test for this scenario 462d1af
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: move these tests to the MetricViewTests.cs