Skip to content
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

Open
heavenly999 opened this issue Aug 21, 2022 · 4 comments
Open

How to send Fluentd's own logs to an output #1075

heavenly999 opened this issue Aug 21, 2022 · 4 comments

Comments

@heavenly999
Copy link

heavenly999 commented Aug 21, 2022

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
@stale
Copy link

stale bot commented Apr 12, 2023

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!

@stale stale bot added the wontfix This will not be worked on label Apr 12, 2023
@pepov pepov added enhancement New feature or request and removed bug Something isn't working wontfix This will not be worked on labels Apr 16, 2023
@pepov
Copy link
Member

pepov commented Apr 16, 2023

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.

@pepov pepov added this to the 4.2 milestone Apr 16, 2023
@stale
Copy link

stale bot commented Jun 16, 2023

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!

@stale stale bot added the wontfix This will not be worked on label Jun 16, 2023
@stale stale bot closed this as completed Jun 23, 2023
@aslafy-z aslafy-z reopened this Jun 23, 2023
@stale stale bot removed the wontfix This will not be worked on label Jun 23, 2023
@pepov pepov modified the milestones: 4.3, 4.x Jul 4, 2023
@stale
Copy link

stale bot commented Sep 2, 2023

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!

@stale stale bot added the wontfix This will not be worked on label Sep 2, 2023
@pepov pepov added pinned and removed wontfix This will not be worked on labels Sep 4, 2023
@pepov pepov modified the milestones: 4.x, 4.8 Jun 14, 2024
@pepov pepov modified the milestones: 4.8, 4.x Jul 1, 2024
@pepov pepov removed this from the 4.x milestone Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants