Pat

Note that SUSE 12 is not a supported platform unfortunately for OSS (some of the Enterprise options do though: https://docs.fluentbit.io/manual/installation/getting-started-with-fluent-bit#enterprise-packages): https://docs.fluentbit.io/manual/installation/supported-platforms The error message looks to be in the dependency...

It should have been caught by the default one so not sure why that didn't work, although maybe a Github issue.

Ah, the configuration seems to specify a user that does not map for me at least: ``` /plugins/in_docker @ashutoshdhundhara ``` So that is likely why, I'll raise a separate issue...

@nandikatlakishore I think you need to look at what your underlying container runtime log looks like - not what the app is producing in the pod. This is what FB...

I would try using the decoders to see if that will un-escape them: https://docs.fluentbit.io/manual/pipeline/parsers/decoders I would also use the `stdout` output plugin to see what they look like to Fluent...

> Also stdout has the same output with misformed json That's fine, my main point was get it correct with this otherwise it'll always be wrong in Kibana - but...

@nandikatlakishore weird, the example log file you show and the docs work perfectly for me, it seems to be providing valid JSON below I think: ```shell $ docker run --rm...

If I add a LUA filter to output the specific key then it looks ok, my only concern is the multiline: ```shell $ docker run --rm -it -v $PWD/:/fluent-bit/etc/:ro fluent/fluent-bit...

Do you mean for the pod there, you seem to be matching on `pod_name` so it should match the logs for that pod? (Assuming that `pod_name` is the actual name...

Yeah probably, really it would be nice to decrement the level after the first report -it's very useful to know when you've messed up your permissions (there are plenty of...