From 37e0d3665724d5ace3c6b346cce5d792bd5890c2 Mon Sep 17 00:00:00 2001 From: Peter Wilcsinszky Date: Fri, 17 Oct 2025 14:20:51 +0200 Subject: [PATCH] event tailer persist is for the position tracking and not for logs Signed-off-by: Peter Wilcsinszky --- .../docs/configuration/extensions/kubernetes-event-tailer.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/configuration/extensions/kubernetes-event-tailer.md b/content/docs/configuration/extensions/kubernetes-event-tailer.md index da2c2134f..8efaa1681 100644 --- a/content/docs/configuration/extensions/kubernetes-event-tailer.md +++ b/content/docs/configuration/extensions/kubernetes-event-tailer.md @@ -131,9 +131,9 @@ NAME READY STATUS RESTARTS AGE sample-event-tailer-0 1/1 Terminating 0 12s ``` -## Persist event logs +## Persist event log position -Event-tailer supports persist mode. In this case, the logs generated from events are stored on a persistent volume. Add the following configuration to your event-tailer spec. In this example, the event tailer is called `sample`: +Event-tailer supports persist mode. In this case, the position of which events have already been processed is stored on a persistent volume. Add the following configuration to your event-tailer spec. In this example, the event tailer is called `sample`: ```bash kubectl apply -f - <