dotnet-observability

To set up OpenTelemetry traces and metrics in an ASP.NET Core API, you configure the OpenTelemetry SDK with ASP.NET Core instrumentation and an OTLP exporter. This enables deep insights into application performance by collecting and exporting request traces and application metrics.

Yes, .NET observability supports Serilog for structured logging. You can configure advanced structured logging using either Serilog or Microsoft.Extensions.Logging to capture detailed application behavior and export it via OpenTelemetry standards.

The best way to implement .NET health checks is by configuring liveness and readiness probes. This ensures robust deployment and orchestration by verifying if the application is live and ready to receive network traffic.

You export .NET application metrics and traces using OTLP by configuring the OpenTelemetry export settings within your application. This setup supports production deployments by sending custom instrumented traces and metrics to an OTLP-compatible backend.

Yes, you can create custom metric and trace instrumentation in .NET. The integration uses OpenTelemetry standards to manually capture specific application performance metrics and traces beyond the default ASP.NET Core instrumentation.

You need both liveness and readiness health checks in .NET to support robust deployment and orchestration. Liveness checks verify the application is running, while readiness checks ensure it is fully prepared to receive traffic without causing errors.