Versions:

Elasticsearch / Kibana:  8.6.0
AWS EKS k8s:  1.24
k8s logging operator:  ghcr.io/banzaicloud/logging-operator:3.17.10

Our logging stack is Elasticsearch => fluentd => Kibana.

Our Kibana dashboards have changed as follows:

• In production, the msg field simply no longer surfaces as an available field by default. Instead, we must use message — a JSON object in which the property msg holds the string we would like to render automatically in the Kibana view.
• In development, the msg field still surfaces as an available default field. However, it no longer yields the service logs we used to see. Those logs, instead, appear to be present in the log.msg property.

Formerly, both in production and development, the msg field was always available.

Why the change? What triggered it? And how can I get back the old behavior — IE, msg field surfaces as a default in the Kibana dashboard? IE, I don’t have to dig into message.msg or log.msg properties to see msg contents.