telemetry-dotnet-entityframework

EF Core query tracing is enabled by integrating OpenTelemetry.Instrumentation.EntityFrameworkCore into your ASP.NET Core application. This automatically captures distributed trace spans for all database queries, including raw SQL text and stored procedure executions, using your existing tracing pipeline.

Yes, you can capture raw SQL statements and stored procedures in EF Core OpenTelemetry traces. The instrumentation automatically records the specific SQL text and execution details for each EF Core database query within the distributed trace spans.

No, EF Core query tracing does not require a separate OpenTelemetry configuration pipeline. The instrumentation integrates seamlessly with your existing OpenTelemetry tracing setup, reusing the shared pipeline without needing additional OTEL environment variable sections.

The best way to debug slow EF Core database queries across microservices is using distributed tracing. By capturing EF Core query execution times and SQL statements via OpenTelemetry, you can pinpoint performance bottlenecks in cross-service data access operations.

You need OpenTelemetry instrumentation for EF Core when monitoring database performance in distributed .NET applications. It is essential for diagnosing slow data access operations, debugging unexpected query behavior, and analyzing cross-service traces for EF Core-powered services.

Tracing EF Core queries with OpenTelemetry focuses on capturing query execution spans and SQL text. It requires a backend service to visualize the traces, and while it highlights slow query performance, it does not automatically optimize poorly written LINQ queries.