-
Notifications
You must be signed in to change notification settings - Fork 177
Add component and unit diagnostics for beats receivers #8991
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
This pull request does not have a backport label. Could you fix it @swiatekm? 🙏
|
# Conflicts: # internal/pkg/agent/application/coordinator/coordinator_test.go # internal/pkg/otel/manager/manager.go
2fe6d75
to
b28331d
Compare
1a4c954
to
25657e7
Compare
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
@swiatekm should we also backport this to 9.1? |
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.
nice seeing diagnostics being formed for otel managed 🙂 Left some comments, have a look and tell me if they make sense
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
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.
code changes LGTM, waiting for the CI to be green 🙂
|
💛 Build succeeded, but was flaky
Failed CI StepsHistory
cc @swiatekm |
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.
LGTM, @swiatekm please report the flaky tests 🙏
* Add diagnostics to otel manager # Conflicts: # internal/pkg/agent/application/coordinator/coordinator_test.go # internal/pkg/otel/manager/manager.go * add integration test * Move helper function to allow diagnostic tests to run on Windows * Handle diagnostics errors separately * Centralize locking for config updates * Make tests more explicit * Early exit from diagnostics generation function * Refactor config generation for easier locking (cherry picked from commit ce0519f)
* Add diagnostics to otel manager # Conflicts: # internal/pkg/agent/application/coordinator/coordinator_test.go # internal/pkg/otel/manager/manager.go * add integration test * Move helper function to allow diagnostic tests to run on Windows * Handle diagnostics errors separately * Centralize locking for config updates * Make tests more explicit * Early exit from diagnostics generation function * Refactor config generation for easier locking (cherry picked from commit ce0519f) Co-authored-by: Mikołaj Świątek <[email protected]>
What does this PR do?
Add the ability for the otel manager to output diagnostics for components and units it runs. This PR doesn't add any actual diagnostic content, just the necessary scaffolding and tests.
The filebeat registry and beat metrics will be added in follow-up PRs.
Why is it important?
Beat receivers need to be covered by diagnostics to ensure issues with them can be effectively diagnosed.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added an entry in./changelog/fragments
using the changelog toolHow to test this PR locally
Build the agent, run it with self-monitoring using beats receivers enabled, and collect diagnostics. You should see the expected directories without any files.
Related issues