the bug should be fixed and included in version 1.10.0 (which is the one you use). We have tests covering .NET 5, so I think the original issue you linked is fixed.
To better troubleshoot this, maybe a few questions:
The problem is that you don't see spans for the SQL queries, right? So there is no sign of the SQL call in the trace? Or are there SQL spans, but some info is missing?
How are your SQL queries generated? You use things like SqlCommand directly (like here), or is it Entity Framework (Core), or some other thing? What I want to get to with this question is that maybe you use something that we currently don't support. Here is a list of DB libraries the agent monitors.
The problem is that you don't see spans for the SQL queries, right?
Exactly! So basically we have gaps in our tracing timelines.
The problem is that you don't see spans for the SQL queries, right?
We're using Dapper.net. For example:
using var connection = await _MySqlConnectionFactory.CreateConnectionAsync();
string statement = "SELECT * FROM some-table";
var result = await connection.QueryAsync<SomeModel>(statement);
I believe Dapper is using DbCommand under the hood.
Implementation of the CreateConnectionAsync is this one:
public async Task<IDbConnection> CreateConnectionAsync() {
var connection = new MySql.Data.MySqlClient.MySqlConnection(GetConnectionString());
await connection.OpenAsync();
return connection;
}
Where MySql.Data.MySqlClient.MySqlConnection comes from the MySql.Data nuget package
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.