Log entries are lost unless a delay is added at the end of the execution for async Task method

Hi,

We are loosing our seq logs for the latest part of our execution unless we add a 3 seconds delay at the end of the application.

LiterateConsoleand RollingFile preserve the logs without needing the delay.

The task is awaited with this style: MyAsyncTask().Wait(); Could you please advise on the issue.

Serilog 2.0.0
Serilog.Sinks.Seq 2.0.0

[mxwlf]

TLDR: call Dispose() on your host.

I know this is very late but if there is still people (like me) that got here with the same problem and found that the solution proposed using CloseAndFlush() by grabbing a reference from static Log is unacceptable in some scenarios (in our case we are following DI service composition rules that dictate strictly pass-on-constructor dependencies and discourage static references):

I was looking to grab any Seq or Serilog factory disposal handle that I could subscribe to the teardown of the program. But I actually found out upon trying first an explicit call to Host.Dispose() that Seq did a good job event-wiring its own disposal to the contextual disposal process inside the Generic Host. And obviously flushing is part of the disposal.

HTH

• Wolf

[nblumhardt]

Hi @chmirenko,

Since Serilog 2.0’s release, you need to add Log.CloseAndFlush() or call Dispose() on the object returned from LoggerConfiguration.CreateLogger() to ensure all buffered writes complete before exiting.

More details in this blog post by @merbla: http://blog.merbla.com/2016/07/06/serilog-log-closeandflush/

Let me know if this doesn’t cover it. Cheers!