-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
bump OpenTelemetry module #9489
Conversation
/triage accepted |
/lgtm With examples=off in build, I guess you are covering examples that new uses may need in docs ! |
Thanks @longwuyuan |
Got it. Thanks |
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.
/lgtm
Thanks
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: esigo, longwuyuan, rikatz The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@esigo just to be on the same page, you are going to follow up on promoting the newly created image right ? |
Yes l'll raise PR shortly. |
What this PR does / why we need it:
Bumps OpenTelemetry to 1.8.1, gRPC to 1.49.2 and otel-nginx module to open-telemetry/opentelemetry-cpp-contrib#252
Types of changes
Which issue/s this PR fixes
fixes #9472
How Has This Been Tested?
Checklist:
Does my pull request need a release note?
Any user-visible or operator-visible change qualifies for a release note. This could be a:
No release notes are required for changes to the following:
For more tips on writing good release notes, check out the Release Notes Handbook