-
Notifications
You must be signed in to change notification settings - Fork 168
Update OTel components to v1.31.0/v0.125.0 #8055
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
base: main
Are you sure you want to change the base?
Conversation
This pull request does not have a backport label. Could you fix it @ycombinator? 🙏
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
Some other dependencies need updating first:
Moving to draft until these updates are made. |
0aff5a9
to
50b810d
Compare
CI (
Long story short, the fix for the above has not yet been released in the github.com/prometheus/prometheus Golang module; it looks like the release is being prepared, though: prometheus/prometheus#16434. So this PR here will be blocked on that release. |
…r/elasticapmconnector
…ic-agent-autodiscover
50b810d
to
b42b547
Compare
|
This pull request is now in conflicts. Could you fix it? 🙏
|
@ycombinator Looks like prometheus tagged a couple new releases already, I can see 3.3.1 and 3.4.0. Does that mean we can unblock this? Thanks. |
What does this PR do?
Updates the OTel components to v1.31.0/v0.125.0.
This update was performed using following command:
It also updates
github.com/elastic/opentelemetry-collector-components/connector/elasticapmconnector
tov0.3.0
to take care of API conflicts amongst dependencies of different versions.Why is it important?
To keep OTel dependencies up-to-date.
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 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