-
Notifications
You must be signed in to change notification settings - Fork 28
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
Fluentd stops sending logs when log_format is set to 'text' #85
Comments
With log level set to trace:
|
@danhale-git Thank you for the issue. I prepared PR which addresses non existing log key. I decided to add warning message as raising exception may lead to re-ingest logs in current architecture |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Edit: Found the issue: I had failed to set
log_key
after the key changed from the defaultmessage
to a non default value.I'm going to leave this open because I think there are some improvements which could have clarified this issue. Unfortunately I have neither the time nor the Ruby experience to open a PR right now.
log_key
value did not exist and I had configuredlog_format=text
which means the expected result should be that no logs are ever sent. I think this is an appropriate situation in which to issue a log, maybe even with levelwarn
informing the user that, for the current chunk, their configuration is useless.I appreciate my suggestions may not be valid for this code. Feel free to close this as my issue related to misconfiguration and has been resolved.
I'm using the kube-logging operator: https://kube-logging.dev/docs/configuration/plugins/outputs/sumologic/
This issue arose as we updated from version 3.17 to 4.20 of the operator.
There are various sumologic related changes in that release, visible by searching in on the page of this very large diff.
kube-logging/logging-operator@release-3.17...4.2.0
However I've come here because the behaviour I'm getting from fluentd based on a single change to the Sumologic output configuration seems unexpected. I hope to get advice on how to move forward with this issue as it seems like a silent failure.
Feel free to close this issue or advise accordingly, I have not confirmed a bug although it does seem like there might be one.
The Sumologic Output is working as expected with
log_format: json
however if I setlog_format: text
fluentd stops sending logs.With
log_format: json
I see fluend logging sends and I see logs in Sumologic.With
log_format: text
I no longer see fluentd logging sends and I no longer see logs in Sumologic.The only change happening in the configuration is the value of
log_format
.I do see buffers under /buffers.
The logging operator deploys three fluentd containers, I am monitoring and inspecting all of them at once when troubleshooting.
I am using the fluentd debug container and everything seems to be functioning as expected except this one puzzling issue. Any advice is very much appreciated.
The text was updated successfully, but these errors were encountered: