Nicholas Blumhardt

Thanks for the suggestion, I think this was raised previously, we can take another look 👍

Hi Vadim, thanks for the suggestion. Right now I think making this change would lead to a lot of downstream churn in monitoring systems and so-on. I agree that the...

Thanks for the follow-up @vhatsura 👍 Right now I still expect the pain caused by a change (especially given that large numbers of monitoring systems work with these events) will...

Aiming to fix this with #287

Version [5.0.0-dev-00259](https://www.nuget.org/packages/Serilog.AspNetCore/5.0.0-dev-00259) of Serilog.AspNetCore should also fix this. If anyone has a chance to test it and confirm - we can push this out as a stable release. Thanks!

Excellent, thanks @FeeSaver 👍

Hi! Thanks for the note. It looks like these [just became opt-in](https://github.com/dotnet/runtime/issues/34305) in .NET 5, and baked into the logger factory itself, to reduce fixed logging overheads. Serilog's ASP.NET Core/hosting...

@naingyelin we'll need to track this, so this ticket is useful, thanks 👍

Thanks, Darcy! The `WebHost.UseSerilog()` call is not correct (should be `Host.UseSerilog()`) - I've written up an example https://blog.datalust.co/using-serilog-in-net-6/ and published a sample repo https://github.com/datalust/dotnet6-serilog-example - perhaps the README could draw...

Thanks for the follow-up @darcythomas; I don't think we need an additional .NET 5 page - we don't currently have pages for .NET 4, Core 1 - 3, etc.. There's...