Update OTel components to v0.120.x

[andrzej-stencel]

What does this PR do?

Updates OTel components to v0.120.0 (core) and v0.120.1 (contrib).

Why is it important?

We should be keeping the components up to date with upstream as much as possible.

OpenTelemetry Collector Contrib updated its github.com/prometheus/prometheus dependency from v0.54.1 to v0.300.1 in v0.120.0 (open-telemetry/opentelemetry-collector-contrib#36873). This resulted in a conflict with Prometheus v0.54.x dependency in Beats. This forced us to temporarily fork the Contrib, revert the v0.300.x update there (elastic/opentelemetry-collector-contrib#3) and import the forked prometheusreceiver module (ca402c6). This resolves the dependency conflict. This was already done on 9.0 branch in #7411 and now we're doing the same thing on main branch.

The plan is to return to upstream, non-forked components as soon as Beats are updated to Prometheus v0.300.x.

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 in ./changelog/fragments using the changelog tool
• [ ] I have added an integration test or an E2E test

How to test this PR locally

go build .
sudo ./elastic-agent otel

[elasticmachine]

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

[andrzej-stencel]

I've created elastic/beats#42748 to resolve the dependency conflict, appreciate any help on this. 🙏

[elastic-sonarqube]

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

[cmacknz]

We can now unblock this using the same approach that was used in #7411

We can pin to v0.120 but to go past that we need beats to update to prometheus v0.300 or keep forking OTel releases which I do not want to do.

[andrzej-stencel]

We can pin to v0.120 but to go past that we need beats to update to prometheus v0.300 or keep forking OTel releases which I do not want to do.

Agree. Updating Beats to Prometheus v0.300 is the way to unblock further OTel updates.

[swiatekm]

This is wrong, but we can merge this PR first, and then the fix alongside #7456.

[andrzej-stencel]

I was thinking you rebase your PR on this PR so that we can prove it's doing the right thing?

[swiatekm]

That PR is now merged, you can rebase on main and regenerate the README.

[elastic-sonarqube]

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]

💔 Build Failed

• Buildkite Build
• Commit: 7a0b729

Failed CI Steps

• x86_64:sudo: default
• x86_64:sudo: default
• x86_64:sudo: default
• arm:sudo: default
• arm:sudo: default
• arm:sudo: default
• x86_64:sudo: default
• x86_64:sudo: default
• x86_64:sudo: default

History

• 💔 Build #19260 failed 21b3e94
• 💔 Build #19258 failed 6b1d715

cc @andrzej-stencel

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b update-otel-v0.120.0 upstream/update-otel-v0.120.0
git merge upstream/main
git push upstream update-otel-v0.120.0

[andrzej-stencel]

Superseded by #7686.