From fa781e04880e7153f38638d15bd1c32d2e79e0de Mon Sep 17 00:00:00 2001 From: Dan Cech Date: Mon, 7 Nov 2022 04:50:22 -0500 Subject: [PATCH] Improve CRI format documentation (#7582) The documentation doesn't mention the flags/tags component in a CRI log line. I went with flags since that's the name it's given in our regex. --- docs/sources/clients/promtail/stages/cri.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/sources/clients/promtail/stages/cri.md b/docs/sources/clients/promtail/stages/cri.md index 5b85ede156..76dca66515 100644 --- a/docs/sources/clients/promtail/stages/cri.md +++ b/docs/sources/clients/promtail/stages/cri.md @@ -17,6 +17,7 @@ space-delimited values with the following components: 1. `time`: The timestamp string of the log 1. `stream`: Either stdout or stderr +1. `flags`: CRI flags including F or P 1. `log`: The contents of the log line No whitespace is permitted between the components. In the following example, @@ -39,7 +40,7 @@ For the given pipeline: Given the following log line: ``` -"2019-04-30T02:12:41.8443515Z stdout xx message" +"2019-04-30T02:12:41.8443515Z stdout F message" ``` The following key-value pairs would be created in the set of extracted data: