Nicholas Blumhardt

Results 931 comments of Nicholas Blumhardt

@conficient thanks for the note! If the events are being forwarded off to some kind of log server, they'll all line up correctly - just in case it wasn't clear...

Hi @tleylan - I don't think client-side adjustment will help, this is a server-side behavior; the client (Blazor) is sending the correct timestamp, but there's no way for the client...

@tleylan I just remembered: https://github.com/nblumhardt/serilog-sinks-timewarp/blob/master/Serilog.Sinks.TimeWarp/Program.cs This would do it: ```csharp Log.Logger = new LoggerConfiguration() .WriteTo.TimeWarp(EveryDayIsLikeSunday, evt => evt.Timestamp.ToLocalTime(), // or ToUniversalTime() writeTo => writeTo.Console()) .CreateLogger(); ``` In an ideal world,...

Thanks for the heads-up 👍 - not sure where/how the problem will be, the base `PeriodicBatchingSink` should be catching and suppressing these: https://github.com/serilog/serilog-sinks-periodicbatching/blob/dev/src/Serilog.Sinks.PeriodicBatching/Sinks/PeriodicBatching/PeriodicBatchingSink.cs#L229 Investigation help/PRs welcome, if anyone has time...

Hi! Thanks for letting me know. I'd be happy to accept a PR if you have any idea why this might be occurring, but I don't have time to investigate...

Thanks for the analysis, @tusanesen :+1: ... wonder if we can fix this, using some other API, now that Blazor has matured a bit?

HI! This sink only supports the `HttpProtobuf` and `Grpc` protocol flavors (`options.Protocol` covers this). What collector are you using that requires HTTP/JSON?

Hi @DevProJSSV, I think this might be something like a "body formatter" - which isn't supported right now, but might also not be needed. The body/message field from a source...

I'm open to the idea of specifying an `ITextFormatter BodyFormatter {..}` option that would support using any of the current Serilog formatters (such as the compact JSON one) to produce...

Thanks for digging into it @RogerVFbr! 👍 I think the property might need to be named `BodyFormatter` to avoid confusion if we at some future point enable the JSON variant...