-
Notifications
You must be signed in to change notification settings - Fork 104
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
Handle connection failed #84
Comments
It happens with graylog connection too. It should not crash the whole rails app because of a third party crash/absence. |
For anyone else that stumbles across this issue from a google search. I ended up changing to UDP to resolve this issue and it seems to correct it. Not getting any rails crashes with a disconnect from graylog. I understand there are reasons you would want to use TCP (security namely), but for our use case it solves the issue. |
We noticed the same issue here. When using TCP mode to connect to Graylog. If we reboot the Graylog server, Our rails app continuously crashes until the Graylog is back up. But when using UDP mode, the rails app stays up and doesn't crash wither the Graylog server is up or down. |
Hello,
The fluentd plugin https://github.com/emsearcy/fluent-plugin-gelf use gelf-rb.
We have a case, when we tried to start fluentd and the graylog server is not reachable.
We have this problem -> emsearcy/fluent-plugin-gelf#28
Is-it possible to handle this exception in your code to let fluentd start and return a specific message or code.
Next, the plugin could handle this situation and try again the connection.
Thanks,
The text was updated successfully, but these errors were encountered: