You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experiencing an issue when Fluentd attempts to send logs to Elasticsearch. The problem seems to be related to parsing the log data. The specific error message is "Failed to parse content to map" and "Invalid UTF-8 middle byte 0x5c", suggesting a possible issue with the encoding of the data being sent to Elasticsearch. This only happens with Nginx Ingress controller logs. Elasticsearch gets like 4 or 5 hits for nginx when it should be around 15K.
To Reproduce
Deploy fluentD on K8S cluster using the Daemonset
Install Ingress Nginx Controller using helm
Add the below config to FluentD
Head over the Kibana and search for nginx-ingress
Expected behavior
Fluentd should correctly send logs to Elasticsearch without encountering parsing errors.
Describe the bug
I'm experiencing an issue when Fluentd attempts to send logs to Elasticsearch. The problem seems to be related to parsing the log data. The specific error message is "Failed to parse content to map" and "Invalid UTF-8 middle byte 0x5c", suggesting a possible issue with the encoding of the data being sent to Elasticsearch. This only happens with Nginx Ingress controller logs. Elasticsearch gets like 4 or 5 hits for nginx when it should be around 15K.
To Reproduce
Deploy fluentD on K8S cluster using the Daemonset
Install Ingress Nginx Controller using helm
Add the below config to FluentD
Head over the Kibana and search for
nginx-ingress
Expected behavior
Fluentd should correctly send logs to Elasticsearch without encountering parsing errors.
Your Environment
Your Configuration
Your Error Log
Additional context
I had added the following config changes to the nginx ingress controller with no luck
Nginx outputs valid Json
The text was updated successfully, but these errors were encountered: