OpenTelemetry.Instrumentation.Http and Application Insights

[juarola]

Hello!

I have a setup where a .net application sends telemetry via out-of-process OTel Collector to Azure Monitor. When i enable HTTP client instrumentation using AddHttpClientInstrumentation and look at the telemetry in AppInsights, outbound spans show up as type "OTHER". When using the official "opentelemetry distro" from microsoft, this problem doesnt occur and AppInsights interprets telemetry correctly.

AppInsights of course has its own data model, so i wonder if there is some attribute i could tag into the telemetry so that it would show up as http. Has anyone else faced this issue or have any ideas how to get this to work?

---

Edit: Digging through code and tests here and in Azure/azure-sdk-for-net + open-telemetry/opentelemetry-collector-contrib repos, i got the dependency type working. Trick was to add a bunch of tags to activity:

• url.scheme
• url.path
• http.scheme
• http.method
• http.host
• http.port

After these tags are present, AppInsights correctly interprets the type as "HTTP". Now there is a bunch of other issues to investigate, as the output in AppInsights still doesn't match what OpenTelemetry Distro creates...

---

Edit 2: Added the same set of attributes to inbound requests and now AppInsights shows them too with proper response codes etc. Without these attributes (one or more of them, didnt bother to check one by one), response code was always 0.

[Kielek]

@rajkumar-rangaraj, do you have any advice here?

[rajkumar-rangaraj]

This question looks is a mis-route to OpenTelemetry .NET Contrib — the behavior you're seeing is related to the OpenTelemetry Collector pipeline, not the .NET instrumentation library.

You will need to move this question to opentelemetry-collector-contrib, since the Collector is responsible for the transformation/export in this scenario.

https://github.com/open-telemetry/opentelemetry-collector-contrib/discussions

Also note that the Azure Monitor exporter used in the Collector does not yet have feature parity with the Azure Monitor Exporter that ships for .NET SDK. This behavior could be one of the current gaps.

If your question is related to the Azure Monitor .NET Exporter or .NET Azure Monitor Distro, please open it in the Azure .NET SDK repo:

https://github.com/Azure/azure-sdk-for-net/issues

For Collector-based Azure Monitor exporter questions, please continue the discussion in the OpenTelemetry Collector Contrib repo.

[juarola]

Thank you for your reply, i had the same thing going on in opentelemetry-collector-contrib too => open-telemetry/opentelemetry-collector-contrib#43929