Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add logrotation section on Running Filebeat on k8s #24120

Merged
merged 2 commits into from
Feb 19, 2021
Merged

Add logrotation section on Running Filebeat on k8s #24120

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
310ac4a
Add logrotation section on Running Filebeat on k8s
ChrsMark Feb 19, 2021
2c8440e
Fix cross-doc link
ChrsMark Feb 19, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions filebeat/docs/running-on-kubernetes.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -233,3 +233,12 @@ annotations:
co.elastic.logs.json-logging/json.add_error_key: "true"
co.elastic.logs.json-logging/json.message_key: "message"
------------------------------------------------

[float]
==== Logrotation

According to https://kubernetes.io/docs/concepts/cluster-administration/logging/#logging-at-the-node-level[kubernetes documentation]
_Kubernetes is not responsible for rotating logs, but rather a deployment tool should set up a solution to address that_.
Different logrotation strategies can cause issues that might make Filebeat losing events or even duplicating events.
Users can find more information about Filebeat's logrotation best practises at Filebeat's
<<file-log-rotation,log rotation specific documentation>>