With dockerd
deprecated as a Kubernetes container runtime, we moved to containerd
. After the change, our fluentbit
logging didn't parse our JSON logs correctly. containerd
and CRI-O
use the CRI Log
format which is slightly different and requires additional parsing to parse JSON application logs.
We couldn't find a good end-to-end example, so we created this from various GitHub issues. There are some features missing (like multi-line logs) and we love PRs.
The original version of this repo used a separate filter to parse the JSON. By changing the cri parser to use the log
field instead of the message
field, the kubernetes filter
converts the JSON if Merge_Log
is set to On
We also had to add two nest filters
to the config to lift
the Kubernetes values to the root level.
config.yaml contains a complete and minimal example configuration using stdout
. We have tested with stdout
and Azure Log Analytics
. While not tested, it should work with Elastic Search
and outher output
providers as well.
You will need to change the
output
match
frommyapp*.*
Note - there are several GitHub discussions on the challenges with multi-line CRI Logs - additional processing is necessary and not included here
In config there are three changes:
time
stream
logtag
and log
time
and stream
map to existing dockerd
log fieldslog
contains the text of the message, which, in our case is JSONkubernetes filter
Merge_Log
must be set to On
Note the regex expression uses
log
for the 4th field, notmessage
[PARSER]
Name cri
Format regex
Regex ^(?<time>[^ ]+) (?<stream>stdout|stderr) (?<logtag>[^ ]*) (?<log>.*)$
Time_Key time
Time_Format %Y-%m-%dT%H:%M:%S.%L%z
nest filters
to lift
the Kubernetes values to the root document
[FILTER]
Name nest
Match kube.*
Operation lift
Nested_under kubernetes
Add_prefix kubernetes_
[FILTER]
Name nest
Match kube.*
Operation lift
Nested_under kubernetes_labels
Add_prefix kubernetes_labels_
Parser
on the input from json
or docker
to cri
[INPUT]
Name tail
Tag kube.*
Path /var/log/containers/*.log
Parser cri
Thank you!
We copied a lot of the yaml from several different GitHub issues / docs including fluentbit docs
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services.
Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines.
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
Any use of third-party trademarks or logos are subject to those third-party's policies.