Nicholas Blumhardt

Hi again! It doesn't look like any other reports or evidence have come in, so my best guess here is that an environmental issue (e.g. some kind of file scanning...

Interesting! Thanks for the report. At first glance it appears most likely to be a race somewhere in _Serilog.Sinks.Async_, I'll shift the issue over to that repo. We've done some...

My first glance impressions were wrong, this is just a case of `Exception.StackTrace` being mutable, and being changed by the rethrow while asynchronously read by the target sink. The general...

`UseSerilogRequestLogging()` has logged exceptions for a long time; adding a new exception handling mechanism (`IExceptionHandler`) hasn't changed that, the example given above is logging the exceptions twice because both the...

Hi! Thanks for the note. Just to clarify, the bug resolved in Serilog 8.0.2 is not a memory leak but rather a shutdown problem which may cause some buffered events...

9.x and 10.x versions address this. Thanks!

Hi! I'd guess those are from a logger with a name like "Grpc" or "Google" - not sure without seeing more of the codebase. This one is a good question...

Hey @tsimbalar! I've also been thinking a bit about `IDiagnosticContext` lately; not exactly from the same angle, but maybe there's some convergence to find; please excuse the brain dump :-)...

@niemyjski if you're on v8 abstractions, use the 8.0.x versions of the _Serilog.Extensions.*_ libraries - it's straightforward and predictable, and has been the versioning policy of these libs for a...

Thanks for dropping me a line. I don't have the time to maintain this one, unfortunately, so forking/embedding in your project may be the best way forwards right now. HTH,...