From 310ac4a368d856e0f1b1b7d72f5ef717329271b0 Mon Sep 17 00:00:00 2001 From: chrismark Date: Fri, 19 Feb 2021 11:48:44 +0200 Subject: [PATCH 1/2] Add logrotation section on Running Filebeat on k8s Signed-off-by: chrismark --- filebeat/docs/running-on-kubernetes.asciidoc | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/filebeat/docs/running-on-kubernetes.asciidoc b/filebeat/docs/running-on-kubernetes.asciidoc index a04fde00ef1c..2190a7368f59 100644 --- a/filebeat/docs/running-on-kubernetes.asciidoc +++ b/filebeat/docs/running-on-kubernetes.asciidoc @@ -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 +https://www.elastic.co/guide/en/beats/filebeat/current/file-log-rotation.html#file-log-rotation[logrotation specific documentation]. From 2c8440e66a58db8ebd53ac707d000a54971efada Mon Sep 17 00:00:00 2001 From: chrismark Date: Fri, 19 Feb 2021 13:14:59 +0200 Subject: [PATCH 2/2] Fix cross-doc link Signed-off-by: chrismark --- filebeat/docs/running-on-kubernetes.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/filebeat/docs/running-on-kubernetes.asciidoc b/filebeat/docs/running-on-kubernetes.asciidoc index 2190a7368f59..1ea7cc6e6d36 100644 --- a/filebeat/docs/running-on-kubernetes.asciidoc +++ b/filebeat/docs/running-on-kubernetes.asciidoc @@ -241,4 +241,4 @@ According to https://kubernetes.io/docs/concepts/cluster-administration/logging/ _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 -https://www.elastic.co/guide/en/beats/filebeat/current/file-log-rotation.html#file-log-rotation[logrotation specific documentation]. +<>