Skip to content
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

[8.x](backport #5838) Update OTel components to v0.112.0/v1.18.0 #5852

Merged
merged 3 commits into from
Oct 25, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 25, 2024

What does this PR do?

Bumps the versions of OpenTelemetry Collector components from v0.111.0/v1.17.0 to just released v0.112.0/v1.18.0.

Why is it important?

We want to use the latest version of OTel components in Elastic Agent. We also need the latest changes in Elasticsearch exporter for Elastic Agent v8.16.

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
    This is an automatic backport of pull request Update OTel components to v0.112.0/v1.18.0 #5838 done by Mergify.

* Update OTel components to v0.112.0/v1.18.0

* fix: bump Elastic Infra Metrics processor to v0.13.0

(cherry picked from commit bf81188)

# Conflicts:
#	go.mod
#	internal/pkg/otel/README.md
@mergify mergify bot requested a review from a team as a code owner October 25, 2024 10:56
@mergify mergify bot removed the request for review from a team October 25, 2024 10:56
@mergify mergify bot added the backport label Oct 25, 2024
@mergify mergify bot requested a review from kaanyalti October 25, 2024 10:56
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Oct 25, 2024
@mergify mergify bot requested a review from pchila October 25, 2024 10:56
Copy link
Contributor Author

mergify bot commented Oct 25, 2024

Cherry-pick of bf81188 has failed:

On branch mergify/bp/8.x/pr-5838
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit bf81188673.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   NOTICE.txt
	new file:   changelog/fragments/1729694636-main.yaml
	modified:   go.sum

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   internal/pkg/otel/README.md

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

@andrzej-stencel andrzej-stencel enabled auto-merge (squash) October 25, 2024 11:11
@pierrehilbert pierrehilbert added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Oct 25, 2024
@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

@andrzej-stencel andrzej-stencel merged commit f08fcf1 into 8.x Oct 25, 2024
15 checks passed
@andrzej-stencel andrzej-stencel deleted the mergify/bp/8.x/pr-5838 branch October 25, 2024 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request 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.

3 participants