-
Notifications
You must be signed in to change notification settings - Fork 981
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kubernetes daemonset can't parse logs - #0 [in_tail_container_logs] pattern not matched #571
Comments
I am running into something similar. I found issue #434 which seems to say that they solution is to use the newest version of the daemonset (v1.12) and use the new cri parser. Not sure if the same thing would help you. |
See also #412
So far I haven't been able to make it work, but I hope it work for others |
Maybe related: I received a similar error with I used to replace tail_container_parse.conf, following the documentation here: https://github.com/fluent/fluentd-kubernetes-daemonset#use-cri-parser-for-containerdcri-o-logs with this content:
Now I use the environment variable instead:
which seems to generate an additional config value After this change, v1.13.2 also works for me. |
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days |
This issue was automatically closed because of stale in 30 days |
For time format issue, I had to add:
Otherwise, I got this error: |
Avoid lots of time to look at fluent#434 and fluent#571
Avoid lots of time to look at fluent#434 and fluent#571
Avoid lots of time to look at fluent#434 and fluent#571 Signed-off-by: Sébastien P <[email protected]>
Describe the bug
When using the Kubernetes daemonset from here the fluentd has issues with "#0 [in_tail_container_logs] pattern not matched" followed by a long string of "////////"
To Reproduce
Expected behavior
Expect logs to be sent to Loggly without error
Your Environment
Kubernetes latest
Your Configuration
Your Error Log
Additional context
Example log line from express app
The text was updated successfully, but these errors were encountered: