Add beat/process config to elastic agent diagnostics collect#29902
Add beat/process config to elastic agent diagnostics collect#29902michel-laterman merged 2 commits intoelastic:masterfrom
Conversation
Add the configs that are output from elastic-agent inspect output to the bundle generated by elastic-agent diagnostics collect. Files are named as ProcID_RouteKey.
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
This pull request does not have a backport label. Could you fix it @michel-laterman? 🙏
NOTE: |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
|
@faec may help in some of your SDHs |
Co-authored-by: Anderson Queiroz <contato@andersonq.eti.br>
|
Changes LGTM, I am been trying to test locally but other stuff is block my build. |
What does this PR do?
Add the configs that are output from elastic-agent inspect output to the
bundle generated by elastic-agent diagnostics collect. Files are named
as ProcID_RouteKey.
Why is it important?
Include the config that's sent from the agent to underlying processes in the diagnostic bundles to allow us to more easily debug config errors.
Checklist
I have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
Start an agent.
Run
elastic-agent diagnostics collectonce the agent is healthyInspect archive's config files.
Related issues