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.
pull/7612/head
Dan Cech 3 years ago committed by GitHub
parent 3c792294d2
commit fa781e0488
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 3
      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:

Loading…
Cancel
Save