Incorrect logs parsing about k8s-monitoring-helm HOT 3 CLOSED

Glad things are working for you!

We're talking about the default parsing format in #100 . I'm going to close this issue in favor of that one.

from k8s-monitoring-helm.

Looking at the differences for logs between now and 0.0.15:

1. We stopped using loki.source.kubernetes in favor of a daemonset and direct log ingestion.
2. cluster label is now set in the external_labels component of loki.write.grafana_cloud_loki
3. Some other changes, but nothing from the default that would have changed parsing.

I'm curious if anything else changed? Are you seeing errors in the grafana-agent-logs pods? Or do things not look right on Loki?

from k8s-monitoring-helm.

Thanks for the fast response!

Thanks to this response, I was able to fix it :)

Since you changed reading logs from daemonset to direct log ingestion, the format has also changed.
Thankfully, there was already a value for configuring loki.process (https://grafana.com/docs/agent/latest/flow/reference/components/loki.process/#stagecri-block)

Changing processor to cri (from docker) fixed this issue, i.e.:

  logs:
    pod_logs:
      loggingFormat: cri

I created a PR with a fix, but I wasn't able to push it :(

from k8s-monitoring-helm.