Added doc on how to handle logrus.Fatalf events #501
Merged
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.
This PR adds some doc on how to handle
logrus.Fatalf
events.When calling
logrus.Fatalf()
,logrus
callsos.Exit(1)
immediately after treating the log. They are two consequences :defer
are ignored;fatal
event to the remote server before the program stops.Fortunately,
logrus.RegisterExitHandler
allows to run arbitrary code before the call toos.Exit
. I propose to add it to thelogrus
example.