Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

EF Core trace stacktraces don't extend into the application

See original GitHub issue

Describe the bug There is something wrong with how stacktraces in awaited async requests get unwound for EF Core in ASP.NET Core. The result is that only system internals are part of the resulting stacktrace, but not the actual method calling the EF Core function.

Example stacktrace as follows:

Elastic.Apm.Model.Span in End
Elastic.Apm.Model.DbSpanCommon in EndSpan
Elastic.Apm.EntityFrameworkCore.EfCoreDiagnosticListener in OnNext
System.Diagnostics.DiagnosticListener in Write
Microsoft.EntityFrameworkCore.Diagnostics.RelationalLoggerExtensions in BroadcastCommandExecuted
Microsoft.EntityFrameworkCore.Diagnostics.RelationalLoggerExtensions in CommandReaderExecutedAsync
Microsoft.EntityFrameworkCore.Storage.RelationalCommand+<ExecuteReaderAsync>d__17 in ExecuteReaderAsync
System.Threading.ExecutionContext in RunInternal
System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1 in MoveNext
System.Threading.Tasks.AwaitTaskContinuation in RunOrScheduleAction
System.Threading.Tasks.Task in RunContinuations
System.Threading.Tasks.Task`1 in TrySetResult
MySqlConnector.Core.CommandExecutor+<ExecuteReaderAsync>d__0 in ExecuteReaderAsync at line 76
System.Threading.ExecutionContext in RunInternal
System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1 in MoveNext
System.Threading.Tasks.AwaitTaskContinuation in RunOrScheduleAction
System.Threading.Tasks.Task in RunContinuations
System.Threading.Tasks.Task`1 in TrySetResult
MySql.Data.MySqlClient.MySqlDataReader+<CreateAsync>d__95 in CreateAsync at line 409
System.Threading.ExecutionContext in RunInternal
System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1 in MoveNext
System.Threading.Tasks.AwaitTaskContinuation in RunOrScheduleAction
System.Threading.Tasks.Task in RunContinuations
System.Threading.Tasks.Task`1 in TrySetResult
MySqlConnector.Core.ResultSet+<ReadResultSetHeaderAsync>d__2 in ReadResultSetHeaderAsync at line 155
System.Threading.ExecutionContext in RunInternal
System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1 in MoveNext
System.Threading.Tasks.AwaitTaskContinuation in RunOrScheduleAction
System.Threading.Tasks.Task in RunContinuations
System.Threading.Tasks.Task`1 in TrySetResult
MySqlConnector.Core.ServerSession+<ReceiveReplyAsyncAwaited>d__78 in ReceiveReplyAsyncAwaited at line 775
System.Threading.ExecutionContext in RunInternal
System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1 in MoveNext
System.Threading.Tasks.AwaitTaskContinuation in RunOrScheduleAction
System.Threading.Tasks.Task in RunContinuations
System.Threading.Tasks.Task`1 in TrySetResult
MySqlConnector.Protocol.Serialization.ProtocolUtility+<<DoReadPayloadAsync>g__AddContinuation|5_0>d in <DoReadPayloadAsync>g__AddContinuation|5_0 at line 484
System.Threading.ExecutionContext in RunInternal
System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1 in MoveNext
System.Threading.Tasks.AwaitTaskContinuation in RunOrScheduleAction
System.Threading.Tasks.Task in RunContinuations
System.Threading.Tasks.Task`1 in TrySetResult
MySqlConnector.Protocol.Serialization.ProtocolUtility+<<ReadPacketAsync>g__AddContinuation|1_0>d in <ReadPacketAsync>g__AddContinuation|1_0 at line 413
System.Threading.ExecutionContext in RunInternal
System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1 in MoveNext
System.Threading.Tasks.AwaitTaskContinuation in RunOrScheduleAction
System.Threading.Tasks.Task in RunContinuations
System.Threading.Tasks.Task`1 in TrySetResult
MySqlConnector.Protocol.Serialization.BufferedByteReader+<ReadBytesAsync>d__2 in ReadBytesAsync at line 55
System.Threading.ExecutionContext in RunInternal

It also seems that the stacktraces are fairly random; sometimes they are there and sometimes not, but I assume this is intentional to reduce the impact of tracing.

To Reproduce Steps to reproduce the behavior:

Configure Elastic APM for ASP.NET Core and EF Core
Execute some action with EF Core queries in it
Check the transaction in ElasticSearch APM

Expected behavior Either collect the stacktrace including the application code, or don’t do stacktraces at all for EF Core; they aren’t exactly cheap.