-
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] Use data subfolder as default for process logs #17960
[Elastic-Agent] Use data subfolder as default for process logs #17960
Conversation
Pinging @elastic/ingest-management (Project:fleet) |
Jenkins test this |
Will this have any effect on where the logs from the processes go? Would be nice if it does as currently it is hard to find the logs for metricbeat for example. |
@ruflin yes this changes the location and logs will go to e.g: |
Is there any reason why we do not use pipeline_name is the name of the output now. This would ensure that a single place contains everything? |
@ph i can change it like this. i did it in this way so we end up with data containing |
pipeline = output name? If yes, sounds confusing to me that we talk in the config about outputs but here about pipline? |
we call it still PipelineID internally in the code, but what it is it is just and output type out of config e.g default/monitoring/elasticsearch/ |
Is it |
in the config you posted it would be default. it is the same value you use when specifying output using |
Its is the |
On your last comment, no preference as long as the logs are easy accessible. |
@michalpristas let's keep it your way :) |
💚 Build SucceededExpand to view the summary
Build stats
|
…ic#17960) [Elastic-Agent] Use data subfolder as default for process logs (elastic#17960)
…logs (#18120) * [Elastic-Agent] Use data subfolder as default for process logs (#17960) [Elastic-Agent] Use data subfolder as default for process logs (#17960) * [Elastic-Agent] Use /tmp for default monitoring endpoint location for libbeat (#18131) * default tmp socket * changelog * Update x-pack/elastic-agent/CHANGELOG.asciidoc Co-authored-by: Pier-Hugues Pellerin <[email protected]> Co-authored-by: Pier-Hugues Pellerin <[email protected]> * Update CHANGELOG.asciidoc * conflicts * go.sum Co-authored-by: Pier-Hugues Pellerin <[email protected]>
What does this PR do?
This PR changes default path for process logs from /var/log to {path.data}/logs
this will conflict with paths CLI PR will need to rebase then
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.