How to stop the log entry from being split into multiple fields #9082
Unanswered
nilushancosta
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have two Kubernetes clusters where I have Fluent Bit and OpenSearch running. I am using Fluent Bit to collect container logs and publish them to OpenSearch. I have a container which logs the following entry
There was a difference in how this log entry was returned from OpenSearch. So I added a new
[OUTPUT]
to fluent bit and had a look at the log from stdout in fluent bit. I noticed a difference as follows.Cluster 1
Cluster 2
As you can see, in Cluster 2, the log entry gets added to a
log
field. So in OpenSearch, the entry is in a field named log. But the same does not happen in Cluster 1. What configuration would cause this? I want to make sure that any log collected by Fluent Bit gets published to a field named log like in Cluster 2.I am using Helm to deploy Fluent Bit. The configmap that gets created has the following configsdroplogs.lua is a custom filter which I use to drop some logs. However it does not modify the log entry like I saw in the output
Beta Was this translation helpful? Give feedback.
All reactions