-
Notifications
You must be signed in to change notification settings - Fork 145
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
[8.17](backport #6113) Update OTel to v0.114.0 #6176
Conversation
* fix: remove Expand converter It has been deprecated since v0.107.0 and was removed in v0.114.0. * sed -i 's/ v0.113.0$/ v0.114.0/' go.mod * sed -i 's/\(go\.opentelemetry\.io\/.*\) v1\.19\.0$/\1 v1.20.0/' go.mod * mage otel:readme * mage notice * add changelog entry * mage notice * update one missed OTel dependency The sed commands didn't update indirect dependencies. * go mod tidy && mage notice (cherry picked from commit 1ab3edc) # Conflicts: # NOTICE.txt # go.mod # go.sum # internal/pkg/otel/README.md # internal/pkg/otel/run.go
Cherry-pick of 1ab3edc 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 |
This pull request has not been merged yet. Could you please review and merge it @andrzej-stencel? 🙏 |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
Quality Gate passedIssues Measures |
What does this PR do?
Update OTel components to v0.114.0.
Why is it important?
We should be keeping the components up to date with upstream.
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