-
Notifications
You must be signed in to change notification settings - Fork 330
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
How to send Fluentd's own logs to an output #1075
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! |
Valid request and sorry for the late reply. Marking this as part of 4.2, but I can't promise it will make it into that release or a later one. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! |
Describe the bug:
As per the documentation, we shouldn't output fluentd's own logs to stdout, instead it should go to a file, which is actually the default setting. Because the logs are no longer in stdout, fluentbit won't collect the logs.
As far as I understand, there is an option to forward only the error log types from fluentd to an existing output reference via the errorOutputRef field. However I would like to forward all types, not only error type logs to an output.
According to fluentd's own documentation, there is an option to collect fluentd's own logs via a label matcher (fluentd labels it's own logs with @FLUENT_LOG), however I couldn't find an easy way to add this part to fluentd's config via the logging-operator.
The question is, how should I forward all of fluentd's own logs to an output?
Expected behaviour:
Be able to collect and forward all of fluentd's own logs
Environment details:
The text was updated successfully, but these errors were encountered: