Nicholas Blumhardt

Thanks for the suggestion! The current design of `SelfLog` assumes that it's only turned on when trying to diagnose a problem; although a lot of people do use it for...

Another quicker and more efficient option might be to just send PRs to the two projects listed in the original report for a conditional "verbose diagnostics" switch - worth serious...

SelfLog is only really intended to be switched on when you're diagnosing a problem, so the current usage is probably correct across the board, to be fair.

I think by its design and intention, `SelfLog` should stay ultra-simple. The goals for `SelfLog` are to provide a debugging mechanism when things go wrong, rather than a general monitoring...

The difference in thinking is might be that to me there _is_ a single good solution for self-logging, it's just not the feature you were originally looking for. SelfLog really...

Hi! I think what you're looking for is covered by https://github.com/serilog-tracing/serilog-tracing, though we haven't tried it out in combination with AppInsights yet. The parent id property there is called `ParentSpanId`....

Thanks for your reply @dtila. Unfortunately there's limited time to dig in deeply on past design decisions here, so I'll close this as we're not expecting it will lead to...

Partially; it's possible to use basic Serilog features today (though the library itself still produces some trim warnings that need suppressing). ```csharp // Works Log.Information("Hello, {Name}!", "world"); ``` Currently, reflection-based...

I believe https://github.com/serilog/serilog/pull/2027 has pushed this forwards.

Seems like a good question to dig into :-) Anyone interested in putting together a _Serilog.Extensions.Telemetry(Abstractions)_ PoC of some sort to explore how functionality in the new annotations might be...