Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[9.0] Remove filebeatreceiver and metricbeat receiver to remove dependency on Beats #7023

Merged
merged 1 commit into from
Feb 26, 2025

Conversation

cmacknz
Copy link
Member

@cmacknz cmacknz commented Feb 25, 2025

What does this PR do?

Removes the filebeatreceiver and metricbeatreceiver and associated tests from the 9.0 branch.

Why is it important?

We need to update our dependency on otel-collector-contrib to get fixes to the elasticsearchexporter that the EDOT collector needs to go GA in 9.0. This update cannot be done because the otel dependency versions in Beats conflicts with the one we need. We can't update the otel dependency versions in Beats without upgraded Beats' dependency on the Prometheus packages, which introduce breaking changes we need time to adapt to. For full details see elastic/beats#42748.

There is no fast fix to this on the Beats side, this is IMO the least bad option. The other quick alternative would be to have Elastic Agent's 9.0 branch point to a feature branch in Beats with the dependency update (so 9.0 here would not point to 9.0 in Beats). That is less disruptive in this repository, but creates another unofficial branch to maintain as long as this situation goes on, and does not prevent this problem happening again with another dependency later that would require more work in the unofficial Beats branch. If it turns out this was the wrong decision, we can switch to the other approach at any time in the future by reverting this commit.

The intent is we'll revert this and bring the beat receiver components back once Beats can safely be updated to the appropriate OTel dependencies.

Disruptive User Impact

None, beats receivers are experimental and unannounced. This change isolates any impact to functionality that isn't meant to be usable externally in 9.0.

Related / blocked issues

@cmacknz cmacknz added Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team skip-changelog labels Feb 25, 2025
@cmacknz cmacknz self-assigned this Feb 25, 2025
@cmacknz cmacknz requested a review from a team as a code owner February 25, 2025 18:56
@cmacknz cmacknz requested review from michel-laterman and swiatekm and removed request for a team February 25, 2025 18:56
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@elasticmachine
Copy link
Contributor

💔 Build Failed

Failed CI Steps

cc @cmacknz

@jlind23 jlind23 merged commit 7f18476 into elastic:9.0 Feb 26, 2025
16 of 17 checks passed
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
skip-changelog Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants