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
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.
Version of Helm and Kubernetes:
Helm Version: 3.12.1
Kubernetes Version:
Client Version: v1.27.2
Kustomize Version: v5.0.1
Server Version: v1.25.9-eks-0a21954
Which version of the chart:
13.9.0
What happened:
When Fluentd attempts to send logs to Elasticsearch, it fails with an error "Failed to parse content to map" and "Invalid UTF-8 middle byte 0x5c". This error appears to be due to issues with the encoding of the log data. This specifically happen with Nginx Ingress Controller logs.
What you expected to happen:
Fluentd should correctly send logs to Elasticsearch without encountering parsing errors.
How to reproduce it (as minimally and precisely as possible):
FluentD helm Values
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.
Version of Helm and Kubernetes:
Helm Version: 3.12.1
Kubernetes Version:
Client Version: v1.27.2
Kustomize Version: v5.0.1
Server Version: v1.25.9-eks-0a21954
Which version of the chart:
13.9.0
What happened:
When Fluentd attempts to send logs to Elasticsearch, it fails with an error "Failed to parse content to map" and "Invalid UTF-8 middle byte 0x5c". This error appears to be due to issues with the encoding of the log data. This specifically happen with Nginx Ingress Controller logs.
What you expected to happen:
Fluentd should correctly send logs to Elasticsearch without encountering parsing errors.
How to reproduce it (as minimally and precisely as possible):
FluentD helm Values
Anything else we need to know:
Getting the error below in fluentd-elasticsearch logs
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: