-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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] Do not require unnecessary configuration #18003
[Elastic-Agent] Do not require unnecessary configuration #18003
Conversation
Pinging @elastic/ingest-management (Project:fleet) |
This look OKay, but let's have #17960 in to test. |
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
|
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, tested with configuration in #17883 from a blank file. Events are sent to Elasticsearch, I also started ES without having Ingest manager creates any templates.
* log paths within data * changelog * removed file * empty config allowed * configuration up to date and unified * changelog * unified * switched path * unnecessary type specifier * logs-output * var run to data path * inject run so meta.json is not created at root of data
…8185) * log paths within data * changelog * removed file * empty config allowed * configuration up to date and unified * changelog * unified * switched path * unnecessary type specifier * logs-output * var run to data path * inject run so meta.json is not created at root of data
What does this PR do?
This PR is based on #17960 and waiting for it to go in.
At the moment when we omit download, retry, process or management.mode section in config agent will panic and die.
This PR allows these section to be empty (skipped) and the only thing needed are configuration of what the user wants to monitor (output and sources)
Why is it important?
To ease up using of standalone agent and not requiring configuration options user does not even understand.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Fixes: #17883