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
I am running a console program and the logs are end to cloudwatch. The console program ends when exception is encountered and exit. I added sleep command to cause the program to sleep for 1 secs so that logs can be send to cloudwatch. Is there a way to handle this gracefully without having to put a wait in every batch program so that logs are not lost.
The text was updated successfully, but these errors were encountered:
I think it would be a great idea to catch the signal termination event, block, attempt to send the logs before shutting down. Logs are important. Someone would need to look into serilog core to see if it supports something like that natively already, because arguably that is where the problem would be. We just take the instructions from the core library on how to send logs, the functionality doesn't really belong in here.
However, it is possible that we are missing some configuration to make sure that happens.
So with that, can I recommend opening a ticket with Serilog Core https://github.com/serilog/serilog, asking for support of this feature. It seems like a great idea.
I'll leave this ticket open while we wait to hear back with what they say.
I am running a console program and the logs are end to cloudwatch. The console program ends when exception is encountered and exit. I added sleep command to cause the program to sleep for 1 secs so that logs can be send to cloudwatch. Is there a way to handle this gracefully without having to put a wait in every batch program so that logs are not lost.
The text was updated successfully, but these errors were encountered: