Support for async/await call stacks in .NET 8

[hokagedami]

Feature Request

With .NET 8's improved async stack trace support, it would be great if the enricher could capture async call stacks more accurately.

Current Behavior

Async call stacks often show incomplete information or generic async state machine methods instead of the actual async method names.

Desired Behavior

Show clean async method names like:

ProcessDataAsync:23 --> ValidateInputAsync:45 --> SaveToDbAsync:12

Instead of:

MoveNext:1 --> SetResult:1 --> MoveNext:1

Use Case

We have a microservice architecture with heavy async usage and the current stack traces make debugging very difficult.

Additional Context

.NET 8 added Environment.StackTrace improvements and StackFrame.GetAsyncMethod() API that might help with this.

Would be happy to contribute to this feature if you can provide some guidance on the approach!

[hokagedami]

This is a great suggestion! I've been working with async heavy workloads and the current stack traces are indeed confusing.

For context, here's what we typically see now:

<>c__DisplayClass0_0.<ProcessAsync>b__0:1 --> AsyncStateMachine.MoveNext:1 --> Task.Run:1

Instead of the much cleaner:

DataService.ProcessAsync:45 --> UserController.HandleRequestAsync:23 --> Program.Main:12

Research findings:

• .NET 8's StackFrame.GetAsyncMethod() does exist and could help
• AsyncStackTrace NuGet package has some good patterns we could adopt
• Would need to detect async methods and resolve the original method names

Implementation idea:

if (frame.GetMethod()?.DeclaringType?.Name?.Contains("<") == true)
{
    // Try to resolve async method name from state machine
    var asyncMethod = frame.GetAsyncMethod();
    if (asyncMethod != null) 
        return asyncMethod.Name;
}

Would love to collaborate on this! I can start a draft PR if you're interested @hokagedami.