Extensibility opportunity for IDiagnosticContext?

Hi there!

Lately I've been thinking about IDiagnosticContext (further from a question I raised on gitter), and how it might be possible to make use of it outside the context of ASP.NET. I thought I'd open this issue to get the conversation started!

It might be worth thinking about this problem in terms of the SerilogTimings library, as it could be a consumer of a more general IDiagnosticContext.

In an ideal world, it might be possible to do this:

var username = "George";
using var operation = Operation.Begin("Updating phone number for {Username}", username);

try {
  // do something
  _diagnosticContext.Set("PhoneNumberValidated", true);

  operation.Complete();
} catch(Exception e) {
  operation.Abandon(e);
}

Which would emit the log:

{
    "@t": "2021-05-28T15:49:51.6627798Z",
    "@mt": "Updating phone number for {Username} {Outcome} in {Elapsed:0.0} ms",
    "@m": "Updating phone number for George completed in 0.0 ms",
    "@i": "c376adfc",
    "@r": ["0.0"],
    "Username": "George",
    "PhoneNumberValidated": true,
    "Outcome": "completed",
    "Elapsed": 0.0001
}

So what would it take to get here? I'm probably going to be pretty far off reality, but from my crude reading of the code:

There needs to be some way to initiate an AmbientDiagnosticContextCollector.Begin to start collecting ambient properties. It feels like this mechanism could handle nested situations where a collection is already in progress (e.g. an operation within another, or operation in an MVC controller). Perhaps if there is a collection already in progress this could be a noop, but maybe you'd want to exclude properties added outside the current call context.
Could this be implemented as an enricher that pulls from the ambient collector? It's a standard way of adding properties, so maybe there could be a way to get an enricher from an IDiagnosticContext to pass to a log event or Operation.Complete()?

To provide a real use case, I'd like to implement an IDiagnosticContext-like mechanism around our message handlers to reduce our log volume and increase cardinality, but currently there's no way to control the lifecycle of this collector so I'd need to implement it all myself.

I'd be keen to push this forward, but I'm a bit unsure of what the implementation of this might look like. What are peoples thoughts?

Thanks!

serilog / serilog-extensions-hosting

Extensibility opportunity for IDiagnosticContext? #47