-
Notifications
You must be signed in to change notification settings - Fork 138
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
[Elastic Agent] Add ability to debug a composable provider #123
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
++ on the proposal. I would skip the |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
@michel-laterman was it part of your diagnosis job? If yes, can we close this?` |
The scope of the outlined issue is more then what is currently included with |
I want to add a little more details here as it relates to diagnostics. Currently The However, I don't think we should name the command that does not contact from to the running agent debug as we tend to use diagnostics and debug interchangeably; maybe add it as a diagnostic subcommand, or add a flag to |
Overview
To help support dynamic inputs elastic/beats#19225 Elastic Agent needs to add the ability to debug the providers using for variable substitution. This issue is to track the debugging effort, for information about variable substitution review elastic/beats#20781
Debugging
This obviously adds a lot of confusion to what the resulting configuration that Elastic Agent will be running with. To ensure that the feature is deployed correctly and that providers are working as expected debugging needs to be a top priority in the implementation.
Debugging the running daemon
With the new ability to communicate with the running daemon the
inspect
command should be changed to talk to the running daemon and return the current configuration that is being used in memory. This will ensure that with running providers like Docker and Kubernetes it is easy to inspect what the resulting configuration is.The current
inspect
andoutput
commands can be combined and moved under thedebug
subcommand. (Note: This is not connecting to the currently running Elastic Agent)Possible to watch the configuration as changes come in with
--watch
.Debugging a single provider
A new
debug
command should be implemented that runs a single provider and output what it's currently providing back to the Elastic Agent. (Note: This is not connecting to the currently running Elastic Agent)Example outputting docker provider inventory key/value mappings:
Example rendering configurations with changes:
The text was updated successfully, but these errors were encountered: