-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
New k8s container logs are not getting picked up by in_tail plugin #3355
Comments
It seems same issue with #3327, I've found following error in your log:
|
Cryptophobia
pushed a commit
to Cryptophobia/kube-fluentd-operator
that referenced
this issue
Apr 27, 2021
- upgrade to fluentd v1.12.3 with latest `in_tail` fixes - fluent/fluentd#3355 - fluent/fluentd#3328 - Changelog: https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#release-v1123---20210423 Signed-off-by: Anton Ouzounov <aouzounov@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Deployed a new k8s pod:
Noticed that no logs are coming from that pod at all, so checked the fluentd logs and there is not a single line from fluentd in_tail plugin. All I see is a bunch of errors from the kubernetes_metadata filter and that is all:
Checked k8s node and the log file exists, but was never picked up by the
in_tail
plugin:To Reproduce
Deploy new k8s pods and monitor the fluentd logs to see if
in_tail
plugin is tailing the new log files or not.Expected behavior
in_tail
plugin should follow defined configuration and pickup new log files as they appear.Your Environment
fluentd 1.12.2
Ubuntu 20.04.1 LTS
5.4.0-62-generic
Your Configuration
Your Error Log
prometheus-vmware-exporter-5475d49bf7-trxnz.log
Additional context
The text was updated successfully, but these errors were encountered: