cri
stage
The cri
stage is a parsing stage that reads the log line using the standard CRI logging format.
Schema
cri: {}
Unlike most stages, the cri
stage provides no configuration options and only
supports the specific CRI log format. CRI specifies log lines log lines as
space-delimited values with the following components:
time
: The timestamp string of the logstream
: Either stdout or stderrlog
: The contents of the log line
No whitespace is permitted between the components. In the following example,
only the first log line can be properly formatted using the cri
stage:
"2019-01-01T01:00:00.000000001Z stderr P test\ngood"
"2019-01-01 T01:00:00.000000001Z stderr testgood"
"2019-01-01T01:00:00.000000001Z testgood"
Examples
For the given pipeline:
- cri: {}
Given the following log line:
"2019-04-30T02:12:41.8443515Z stdout xx message"
The following key-value pairs would be created in the set of extracted data:
content
:message
stream
:stdout
timestamp
:2019-04-30T02:12:41.8443515
Related Enterprise Logs resources
Grafana Enterprise Logs: Logging with security and scale
Join us for this webinar, which will cover: Challenges with logging as organizations scale and the volume of logs explodes, how Grafana Enterprise Logs enables organizations to make logs available to any team members who need them, features available in GEL and how to get access, a live product demo so you can see GEL for the first time
VIDEO: Watch this first-look demo of the new Grafana Enterprise Logs
Based on Loki, Grafana Enterprise Logs is part of the Grafana Enterprise Stack for composing and scaling observability on your own infrastructure.
Introducing Grafana Enterprise Logs, a core part of the Grafana Enterprise Stack integrated observability solution
Powered by the Loki open source project, the Enterprise Logs offering joins metrics and dashboards in our enterprise-ready stack for self-managed observability.