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
[x ] (optional) already reported 3rd party upstream repository or mailing list if you use k8s addon or helm charts.
Problem
We've been facing some major issues in production lately that we have tracked down to several types of logs that are getting collected with non UT8 encoded characters. It seems like once fluentd hits one of these logs, all logs stop getting delivered to elasticsearch. Here is the error from one of the logs:
This then goes into a loop of trying to deliver this forever. I think we probably have an issue here with these logs that we aren't sure yet how to fix (open to suggestions) but the issue we are seeing with fluentd is that all logs stop shipping to elasticsearch once fluentd goes into this state. We can see buffer chunks building on the fluentd pod but never getting delivered.
Is there a way to force UTF-8 encoding in this plugin?
Because of this we've gotten into a very unstable state with fluentd and are constantly seeing instabilities and issues with it in our production environment. Any help would be much appreciated.
(check apply)
Problem
We've been facing some major issues in production lately that we have tracked down to several types of logs that are getting collected with non UT8 encoded characters. It seems like once fluentd hits one of these logs, all logs stop getting delivered to elasticsearch. Here is the error from one of the logs:
This then goes into a loop of trying to deliver this forever. I think we probably have an issue here with these logs that we aren't sure yet how to fix (open to suggestions) but the issue we are seeing with fluentd is that all logs stop shipping to elasticsearch once fluentd goes into this state. We can see buffer chunks building on the fluentd pod but never getting delivered.
Here is our config:
Is there a way to force UTF-8 encoding in this plugin?
Because of this we've gotten into a very unstable state with fluentd and are constantly seeing instabilities and issues with it in our production environment. Any help would be much appreciated.
Steps to replicate
Either clone and modify https://gist.github.com/pitr/9a518e840db58f435911
OR
Provide example config and message
Expected Behavior or What you need to ask
fluentd to continue to process logs after a log gets rejected
...
Using Fluentd and ES plugin versions
FROM fluent/fluentd:v1.15-debian-1
k8s
Elasticsearch 8.7.0
The text was updated successfully, but these errors were encountered: