Cherry-pick #24120 to 7.11: Add logrotation section on Running Filebeat on k8s#24127
Merged
ChrsMark merged 1 commit intoelastic:7.11from Feb 19, 2021
Merged
Cherry-pick #24120 to 7.11: Add logrotation section on Running Filebeat on k8s#24127ChrsMark merged 1 commit intoelastic:7.11from
ChrsMark merged 1 commit intoelastic:7.11from
Conversation
(cherry picked from commit ea5d413)
Contributor
|
Pinging @elastic/integrations (Team:Platforms) |
jsoriano
approved these changes
Feb 19, 2021
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪❕ Flaky test reportNo test was executed to be analysed. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 #24120 to 7.11 branch. Original message:
What does this PR do?
This PR adds logrotation section on docs about
Running Filebeat on Kubernetes. This is part of action items to cover logrotation issues occurring to users running Filebeat on Kubernetes.Why is it important?
Users that are not aware of logrotation on their k8s clusters might face issue with lost or duplicate events.
@jsoriano @kvch let me know what you think.