Nicholas Blumhardt

Thanks, nice spotting 👍

The second line, `builder.Services.AddLogging(...` should not be necessary after calling `builder.Host.UseSerilog(`. Only one or the other is necessary. HTH!

Good news! The core forwarding functionality is now in the (`dotnet tool` installable) prerelease versions of `seqcli`. There's some basic documentation in: https://github.com/datalust/seqcli/tree/dev?tab=readme-ov-file#store-and-forward-ingestion-proxy-preview The `seqcli forwarder` command group is also...

Thanks for the nudge, @otodata-fcourchesne 👍

Hi @cmhernandezdel, thanks for your message. This is most likely a build issue; I'm not 100% sure how this hangs together around `netstandard2.1` but you may be able to sort...

Thanks for the note! I've updated the example now. It's not likely we'll add these types back to the public API surface, though some constants would be nice for the...

Thanks for checking in first, deeply appreciated 👍 👍 I think if the extent of the change was: * Modify `SelectTheme` to consider the `NO_COLOR` variable, * Leave `applyThemeWhenOutputIsRedirected` as...

Hi @ArieGato, The switch to the Serilog 4 batching configuration looks good 👍 I've been doing some work on a built-in fallback-logging implementation that seems like it would streamline how...

Hi! The `formatter` and `outputTemplate` options aren't compatible; if you want to customize the JSON format you might best look at using `formatter` with `ExpressionTemplate`. This post has recipes for...

Hi! This combination of targets and packages works fine for me, and given the large amount of Serilog usage on .NET 4.8 it's likely we'd see more reports if the...