You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does it support force flush method? E.g. in order to be sure that all logs have been delivered in case of process exit or graceful shutdown.
Or does it support pino's .flushSync() or .final()?
The text was updated successfully, but these errors were encountered:
Correct me if I'm wrong please, but the way I understand the transport should be used as a separate process, so pino's .flushSync() or .final() does not affect the transport. It just ensures that the last logs get out to the transport prior to exit.
So then your first question is a good one. The pino-cloudwatch stream should flush on graceful shutdown or process exit. But I don't have any tests around that at the moment so I can't guarantee it.
I don't know exactly, just thought that pino might send some special keyword that could tell transport that parent process is about to finish and it's time to send data if it's buffered in transport.
Also cloudwatch transport may be used in lambdas, where there is no possibility to run transport like outside the main app. So it's needed to be used inside app, like in example of WritableStream https://github.com/dbhowell/pino-cloudwatch#writable-stream.
So I think to make sure that this transport will not eat last logs from app, it should provide some .flush (which could be called when using this transport inside main application) method and listen to exit signals as well and call that method when it receives them.
Hi, First of all thanks for such pino module.
Does it support force flush method? E.g. in order to be sure that all logs have been delivered in case of process exit or graceful shutdown.
Or does it support pino's
.flushSync()
or.final()
?The text was updated successfully, but these errors were encountered: