Does the OpenTelemetry Feature clash with Microsoft.ApplicationInsights at all?

[bh3605]

Microsoft's application insights package recently added an update to support full message tracing. microsoft/ApplicationInsights-dotnet#2593

Our company's current state is we are using the incoming/outgoing message tracing feature from one of your samples.

In regards to the OpenTelemetry feature, do these two play nicely with each other? AI now shows full message tracing. Does the OpenTelemetry feature also show full message tracing? If yes, should I write a filter to block all service bus telemetry emitted from Microsoft's Application Insights package?

[ramonsmits]

@bh3605 It depends on what you mean with clash. NServiceBus CAN create/emit activities if OpenTelemetry is configured to generate them for the NServiceBus namespace via .AddSource("NServiceBus.*").

Some users might not want both NServiceBus + ApplicationInsights Azure Service Bus activities as that could result in a lot of trace data.

[bh3605]

By clash I meant duplicate traces whose information overlaps. Clash is the wrong word here. Overlap is what I'm really asking about.