Call logtail.flush() when LogtailTransport (winston) is closed #118
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.
We started using
@logtail/node
withwinston
and noticed that when a winston logger closes,LogtailTransport
does not flush buffered messages tologtail
. This is especially annoying when trying to log unhandled exceptions that cause the process to exit.The base winston
Transport
class accepts aclose()
callback in the constructor options object, which is called whenever the transport instance is "unpiped" from the logger. This PR wraps anyclose()
callback passed to the constructor ofLogtailTransport
with the flushing logic.This PR also adds a unit test for
LogtailTransport
. This test fails without the changes in the constructor.