-
Notifications
You must be signed in to change notification settings - Fork 169
[9.0] Use elastic apm connector to replace other apm components #7172
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
Bump to latest, update license and tidy
[For reviewers] I haven't added a changelog file since there are no end-user changes but let me know if I need to add one. |
4508e77
to
e0b324e
Compare
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
💚 Build Succeeded
History
cc @lahsivjar |
(cherry picked from commit efeb73b) # Conflicts: # NOTICE.txt # go.mod # go.sum # internal/pkg/otel/README.md
(cherry picked from commit efeb73b) # Conflicts: # NOTICE.txt # go.mod # go.sum # internal/pkg/otel/README.md
… (#7452) (cherry picked from commit efeb73b) # Conflicts: # NOTICE.txt # go.mod # go.sum # internal/pkg/otel/README.md Co-authored-by: Vishal Raj <[email protected]>
@@ -23,16 +23,15 @@ require ( | |||
github.com/elastic/go-sysinfo v1.15.1 | |||
github.com/elastic/go-ucfg v0.8.8 | |||
github.com/elastic/mock-es v0.0.0-20241101195702-0a41fa3d30d9 | |||
github.com/elastic/opentelemetry-collector-components/connector/signaltometricsconnector v0.3.0 | |||
github.com/elastic/opentelemetry-collector-components/connector/elasticapmconnector v0.2.0 |
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.
any reason this was not changed to v0.2.1? like it was changed on main branch?
https://github.com/elastic/elastic-agent/blob/main/go.mod#L28
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.
It was probably missed since the PR has been open for a long time, however, the main is on v0.121.0 whereas 9.0 is on v0.120.0 for upstream components (at least when the PR was created). The update to the apm connector for v0.2.1 was mainly to allow upgrading to the newer version so it is not critical to get this in. Are you facing any issues?
What does this PR do?
The PR replaces
lsminterval
processor andsignaltometrics
connector with the newly introducedelasticapm
connector which wraps both the processor and the connector with the required APM configurations.In addition, the PR also removes aggregation for metrics pipeline as required by elastic/opentelemetry-collector-components#390
The PR is same as #6937 but for 9.0 branch since the upgrade of otel components to version 0.120.0 has been merged to 9.0 already however, the main PR is still pending.
Why is it important?
To centralize all APM components and configurations a new connector component called elasticapmconnector was recently introduced. The component encapsulates the signaltometrics connector and the lsminterval connector along with the required configurations for APM.
To handle metrics-only services correctly for the UI.
Checklist
- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry in./changelog/fragments
using the changelog tool- [ ] I have added an integration test or an E2E testDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself