[9.1](backport #46464) chore: update OTel Collector libraries to v1.41.0/v0.135.0#46781
Conversation
* chore: update OTel Collector libraries to `v1.41.0`/`v0.135.0` * fix(auditbeat): update ebpfevents to `v0.8.0` Resolves dependency conflict on github.com/cilium/ebpf. * make notice * test: fix TestFilebeatOTelE2E integration test The property `flush_timeout` has been required since v0.134.0. I believe this is a result of fixing config validation in open-telemetry/opentelemetry-collector#13611. * test: fix unit tests (cherry picked from commit 16c4d9a) # Conflicts: # NOTICE.txt # go.mod # go.sum
|
Cherry-pick of 16c4d9a 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 |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
|
This pull request has not been merged yet. Could you please review and merge it @andrzej-stencel? 🙏 |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
|
This pull request has not been merged yet. Could you please review and merge it @andrzej-stencel? 🙏 |
|
This pull request has not been merged yet. Could you please review and merge it @andrzej-stencel? 🙏 |
|
There is something strange here @pkoutsovasilis do you know what could lead us to use this old version? |
|
@pierrehilbert although not fully familiar with beats CI, I do believe that this is the reason you see here 9.1.2 for the FIPS ECH integration tests |
Proposed commit message
Updates the OpenTelemetry Collector dependencies to the current latest versions v1.41.0/v0.135.0. See changelogs since
v1.36.0/v0.130.0for Core and Contrib.Why is it important?
We want to be on the latest version to keep up with latest features and bug fixes.
Checklist
[ ] My code follows the style guidelines of this project[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] 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[ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally