How to send Fluentd's own logs to an output

[heavenly999]

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:

• Kubernetes version (e.g. v1.15.2): v1.21.1
• Cloud-provider/provisioner (e.g. AKS, GKE, EKS, PKE etc): On-premise
• logging-operator version (e.g. 2.1.1): 3.17.7
• Install method (e.g. helm or static manifests): helm

[pepov]

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.