Cherry-pick #19811 to 7.x: [Elastic Agent] Send Agent logs to elasticsearch #19898
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Work on logging twice. * Work on agent logging to fleet. * Commit example index strategy. * More work on logging to ES. * Revert change to release/version.go * Fix indexes for metricbeat sidecars. * Add to changelog. * Fix fmt. * Don't expose zapLevel, add ConfigureWithOutputs. * Update comment. * Update comment. (cherry picked from commit 2297636)
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cherry-pick of PR #19811 to 7.x branch. Original message:
What does this PR do?
Agent will now always log to
${path.data}/logs/elastic-agent-json.logno matter the settings fromelastic-agent.yml(those still apply, for the user specified choice). With monitoring always on Filebeat will always be started and will send the logs from${path.data}/logs/elastic-agent-json.logto elasticsearch.The spawned filebeat and metricbeat now log to
filebeat-json.logandmetricbeat-json.login JSON format and forward to elasticsearch.Indexes:
logs-elastic.agent-default{logs,metrics}-elastic.agent.filebeat-default{logs,metrics}-elastic.agent.metricbeat-defaultWhy is it important?
So all logs of the Elastic Agents on hosts are in elasticsearch so monitoring/troubleshooting of the Fleet is much easier.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues