Rolf Kristensen

@vasily-kirichenko Try updating to latest Akka.Logger.NLog 1.3.1: https://www.nuget.org/packages/Akka.Logger.NLog/ It should improve the logger-names for NLog. Alternative use `${event-properties:item=logSource:whenEmpty=${logger}}` instead of just `${logger}`.

@TheXenocide You are very welcome to create a pull-request with your ideas.

Pre-Release from #816 is available here: https://ci.appveyor.com/project/nlog/nlog-web/builds/44420816/artifacts If people want to help test/verify/review the direction. The following middleware must be enabled: ```csharp app.UseMiddleware(); ``` @jdpapiero @jenunez @david-pierola-incontact @muchachopolo @ferd-altamirano @marcos-bustos-nice...

Curious how this works together with AsyncTargetWrapper. The NLog Layout provides automatic context-capture, but now you have to implement everything yourself. But it also seems that the original NLog.Web-module is...

@bakgerman Curious if you have ever used this code on ASP.NET Core Application? Or if you are just picking up a challenge? I'm guessing the goal of this buffering-wrapper is...

Think it would make most sense if there was only one `AspNetBufferingTargetWrapper`, but depending on target-platform, then it hooked up to Http-Module or Http-Middleware. Maybe the Http-Module and Http-Middleware could...

Yes a static flush method on AspNetBufferWrapper would be good (Taking the HttpContext as input-parameter)

The callstack doesn't seem to include any Sentry-classes: ``` at automate.logging.NLogLogger.Fatal(Exception x, Boolean LogExtern) in D:\sources\automate\automate.logging\NLogLogger.cs:line 214 at automate.App.ApplicationStartup(Object sender, StartupEventArgs e) in D:\sources\automate\automate\App.xaml.cs:line 1074 at System.Windows.Application.OnStartup(StartupEventArgs e) at System.Windows.Application.b__1_0(Object...

Do not think anyone has made a XSD-Schema for the ElasticTarget. The easy way of getting rid of the warning is changing `xsi:type="ElasticSearch"` to `type="ElasticSearch"` (removing `xsi:`-prefix).

The bug is in NEST / Elastic-Client and not in the NLog-target. You should report the bug elsewhere. Alternative you can try and protect yourself from the very fragile Json-Serializer...