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.
feat: [Internal] open telemetry built in metrics for GRPC #3709
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
feat: [Internal] open telemetry built in metrics for GRPC #3709
Changes from all commits
5806943
4329770
1f87e91
c18fec2
7b6c0a7
01adb67
70ff8bf
80d3017
b2f4293
5b29243
64e02f7
1801433
94e8161
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.
Curious - why are we skipping this. Did we fix the issue that a instance id could be missing (because we will set "unknown" by default?).
My concern is that if there is a bug that causes the instance id not to be correctly populated, we won't be able to catch that regression.
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.
Earlier instance_id was only getting set from
HeaderInterceptor
, so there were cases wheninstance_id
was null in cases when we dont receive a response header.Now since we have added a default "unknown", we don't need this check.
We can catch regression by
ITBuiltInMetricsTest
which checks for data as per the filtered query and one of the filter is "instance_id"