log pattern on k3s containerd

[chart2023]

I have a problem about log format from /var/log/pods of pod on k3s Containerd because I cannot analyze these logs from pods efficiently because it separates each line
for example.

2024-10-19T02:28:52.222540932Z stdout F [Symbol(shapeMode)]: false,
2024-10-19T02:28:52.22254504Z stdout F [Symbol(kCapture)]: false,
2024-10-19T02:28:52.222549317Z stdout F [Symbol(kBytesWritten)]: 0,
2024-10-19T02:28:52.222553423Z stdout F [Symbol(kNeedDrain)]: false,
2024-10-19T02:28:52.222557757Z stdout F [Symbol(corked)]: 0,
2024-10-19T02:28:52.222562039Z stdout F [Symbol(kOutHeaders)]: [Object: null prototype],
2024-10-19T02:28:52.222583673Z stdout F [Symbol(errored)]: null,
2024-10-19T02:28:52.222588514Z stdout F [Symbol(kHighWaterMark)]: 16384,
2024-10-19T02:28:52.222592722Z stdout F [Symbol(kRejectNonStandardBodyWrites)]: false,
2024-10-19T02:28:52.222596782Z stdout F [Symbol(kUniqueHeaders)]: null
2024-10-19T02:28:52.222600771Z stdout F },

Actually, this log occur from the same event, but it was separate into multiple line. When I use fluent-bit to send these log to loki or amazon cloudwatch, I cannot analyze these logs because it difficult to read.

However, I found log from K3S in docker mode has been JSON formatted. For example

{"log":"2024-10-19 04:06:37,098 [TB-Scheduling-1] INFO o.t.s.s.s.DefaultTbEntityDataSubscriptionService - Stats: regularQueryInvocationCnt = [0], regularQueryInvocationTime = [0], dynamicQueryCnt = [2] dynamicQueryInvocationCnt = [1], dynamicQueryInvocationTime = [20], alarmQueryInvocationCnt = [0], alarmQueryInvocationTime = [0]\n","stream":"stdout","time":"2024-10-19T04:06:37.098476003Z"}

Please give me an advise to set log format in k3s containerd

[brandond]

This is a containerd issue, not K3s. Ref:

• Configure log to JSON format for container logs using shim logging plugin containerd/containerd#4186