Open samcarton opened 1 week ago
Hi @samcarton, at this moment the only way to disable this is to set DD_TRACE_OTEL_ENABLED
to false
(if it is enabled), unfortunately this would disable the OpenTelemetry support within the .NET Tracer as well.
Thanks for raising this though as we will look into improving this as this isn't ideal.
Describe the bug
Npgsql
- in this instance there is an issue withNpgsql
where multiplexing and open telemetry tracing are causing runaway CPU and memory issues.DD_TRACE_Npgsql_ENABLED=false
does cause datadog to ignore traces produced byNpgsql
Npgsql
ActivitySource
in theIgnoreActivityHandler
,Npgsql
is still producing the traces, and still causing runaway CPU and memory issues.Npgsql
side, but in the meantime we appear to have no way to turn off the problematic tracing.Ignored
integration to disable tracing for that integration entirely, whatever your reason for doing so may be.To Reproduce Steps to reproduce the behavior:
DD_TRACE_Npgsql_ENABLED=false
Expected behavior
Runtime environment (please complete the following information):
<PackageReference Include="Datadog.Trace" Version="2.45.0" />