Skip to content

[9.0](backport #7867) [Chore] Improve error reporting when otel collector fails to start #7875

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 2 commits into
base: 9.0
Choose a base branch
from
Open

[9.0](backport #7867) [Chore] Improve error reporting when otel collector fails to start #7875

wants to merge 2 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 16, 2025

What does this PR do?

If OTel collector fails to start say due to incorrect config - the logs do not output what went wrong. The only way to know that is by using elastic-agent status command.

This PR logs such errors.

Why is it important?

Improve error logging when collector fails to start

Checklist

  • I have read and understood the pull request guidelines of this project.
  • 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 #7867 done by [Mergify](https://mergify.com).

@khushijain21 @mergify
[Chore] Improve error reporting when otel collector fails to start (#…
f0db871 
…7867)

* [Chore] Improve error reporting when otel collector fails to start

* fix the log message

(cherry picked from commit 9dea232)
@mergify mergify bot requested a review from a team as a code owner April 16, 2025 16:06
@mergify mergify bot added the backport label Apr 16, 2025
@mergify mergify bot requested review from michalpristas and swiatekm and removed request for a team April 16, 2025 16:06
@khushijain21 khushijain21 enabled auto-merge (squash) April 17, 2025 04:40
@khushijain21
Copy link
Contributor

/test

@elastic-sonarqube Elastic SonarQube
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
33.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

@elasticmachine
Copy link
Contributor

elasticmachine commented Apr 17, 2025 •
edited
Loading

💔 Build Failed

Failed CI Steps

History

cc @khushijain21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@khushijain21 khushijain21 khushijain21 approved these changes

@michalpristas michalpristas Awaiting requested review from michalpristas michalpristas is a code owner automatically assigned from elastic/elastic-agent-control-plane

@swiatekm swiatekm Awaiting requested review from swiatekm swiatekm is a code owner automatically assigned from elastic/elastic-agent-control-plane

Assignees

@khushijain21 khushijain21

Labels
backport skip-changelog
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@khushijain21 @elasticmachine