No tracing for database failures
Bug Report
List of all OpenTelemetry NuGet
packages and version that you are
using (e.g. OpenTelemetry 1.0.2):

Expected behavior : - The expected behavior I wanted was to see all the database traces even in case of failures.
What did you expect to see? I want to see the reason for the failure in databases and also receive a message based on the failure during the time of the call.
Actual behavior : -
The current behavior that is being seen is that all database success traces are being available via the jaeger and zipkin exporters.

But the failure of any database does not generate any traces.

What did you see instead?
I have been seeing that sql auto instrumentation has been working only during the success calls between the application and databases. Which is also visible in the console output provided by the application.
