[8.19] (backport #8991) Add component and unit diagnostics for beats receivers #9051
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
This is an automatic backport of pull request #8991 done by [Mergify](https://mergify.com).