ADO.NET auto-tracing should support other DbCommand.ExecuteXXX methods about dd-trace-dotnet

[EricStG]

Any update on this? In our case, missing ExecuteNonQuery and ExecuteScalar is really hurting the value we get out of APM.

[mikesigs]

This is a pretty critical issue. The documentation says that ADO.NET is automatically instrumented. But given that only one of it's methods (of perhaps a dozen) are actually being instrumented makes this a fairly misleading claim.

Unless this issue has just been mistakenly not kept up to date with work that has actually been done, it's pretty unfortunate that it has sat here since last November with no movement at all.

[andrewsouthard1]

Hey @mikesigs and all - thanks again for flagging this. We will begin to add this to our existing integration starting next week - once we have a release(or a pre-release if your teams want to try) - I will reach out on this issue.

[lucaspimentel]

With release 1.8, we now instrument the ExecuteReader(), ExecuteScalar(), and ExecuteNonQuery() methods (and their async versions) on DbCommand and SqlCommand.

I created a separate GitHub issue (#534) to track adding auto-instrumentation to SqlCommand.ExecuteXmlReader().

[lucaspimentel]

Thanks, @rlaveycal! This is known limitation and will be addressed soon.

[mikesigs]

Thanks @andrewsouthard1. Count us in for the pre-release. We'll give it a shot. However, we're on a time-sensitive POC of Datadog right now. So depending on how soon the pre-release is, we may or may not still need it.

Thanks for the update!

[mikegatmcg]

@andrewsouthard1 My company would also like to get this working. Please reach out when you have something to try. FYI, we've been working with a team of folks at DD about moving 3 integrations to DD. It was decided to get the 2 others going first (easy wins) before figuring out the APM side.