This repository was archived by the owner on Nov 2, 2018. It is now read-only.
It is possible to notice if Graylog connection is lost. #36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…errors. (For example TCP connection lost).
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Originally EasyGelf swallows all exceptions.
I want to use EasyGelf with TCP-protocol to get connection lost -errors.
I have NLOG fallbackgroup that should notice if Graylog connection is lost.
In case of failure it should change to next log target.
If all errors are handled inside EasyGelf, target is never changed in NLOG fallbackgroup.
So these changes makes possible to use EasyGelf with NLOG fallbackgroup.