-
Notifications
You must be signed in to change notification settings - Fork 197
[8.19] (backport #10391) feat: update OTel Collector components to v0.137.0 #10543
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
Conversation
Cherry-pick of 7ea323e has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
We'd need to backport #10378, but reading the comments in that PR, I'm not sure what the final decision was. @gregkalapos are we still replacing the elastic trace processor with a shim? |
This pull request is now in conflicts. Could you fix it? 🙏
|
424ae8f
to
386af85
Compare
* sed -i 's/\(go\.opentelemetry\.io\/collector.*\) v0\.135.0/\1 v0.137.0/' go.mod * sed -i 's/\(go\.opentelemetry\.io\/collector.*\) v1\.41\.0/\1 v1.43.0/' go.mod * sed -i 's/\(github\.com\/open-telemetry\/opentelemetry\-collector\-contrib\/.*\) v0\.135\.0/\1 v0.137.0/' go.mod * go mod tidy * update Elastic components * remove Elastic Trace processor In anticipation of #10378 * go get go.opentelemetry.io/[email protected] * go mod tidy * add changelog entry (cherry picked from commit 7ea323e) # Conflicts: # NOTICE-fips.txt # NOTICE.txt # go.mod # go.sum # internal/pkg/otel/README.md
386af85
to
b308fb9
Compare
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.
No conflicts, looks good.
What does this PR do?
Updates the OpenTelemetry Collector dependencies to the current latest version
v0.137.0
. See changelogs sincev1.41.0
/v0.135.0
for Core and Contrib.Also updates Elastic OTel components to versions compatible with upstream
v0.137.0
.Why is it important?
We should be keeping the OTel components up to date with upstream as much as possible.
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works./changelog/fragments
using the changelog tool[ ] I have added an integration test or an E2E testHow to test this PR locally