Epic: .NET Developers have a great observability & diagnostics experience for cloud-native applications

[samsp-msft]

Developing cloud native applications is about more than being able to create a containerized application that can handle WebAPI requests. The application needs to participate in the cloud native ecosystem.

Applications need to be able to easily implement the 3 pillars of observability:

• Logging
• Metrics
• Distributed Tracing

And egress those artifacts to appropriate storage and analysis environments so that SRE can monitor the health of the service, and ideally be able to detect and rectify issues before they have an adverse effect on the service's customers.

When issues are identified with the service, or the service developers are looking for how to improve the performance and reliability of the service, they need to be able to collect and analyze diagnostic information such as:

• Crash dumps
• Memory dumps & GC Dumps
• Detailed traces of what is happening inside the service for performance & diagnostics purposes.

Finally, when all else fails, developers need to be able to debug their services in the production environment.

We have been building parts of these stories in the previous releases of .NET. In .NET 8 we need to bring those pieces together and fill the gaps to provide a coherent story for cloud native developers in .NET.

• User Story: Cloud Native developers have the tools to be able to collect traces and dumps in container environments and perform 1st level analysis on them #3761
• User Story: .NET developers have a first-class experience for observability using Open Telemetry in their applications #3762

[eerhardt]

Can this issue be closed? Or is there more work this is tracking?