Skip to content

Latest commit

 

History

History
34 lines (22 loc) · 1.92 KB

opentelemetry-troubleshooting-dotnet.md

File metadata and controls

34 lines (22 loc) · 1.92 KB
Raw
title description ms.date editor ms.service ms.devlang ms.reviewer ms.custom
Troubleshoot OpenTelemetry issues in .NET
Learn how to troubleshoot OpenTelemetry issues in .NET. View known issues that involve Azure Monitor OpenTelemetry Exporters.
06/24/2024
v-jsitser
azure-monitor
csharp
mmcc, lechen, aaronmax, v-leedennis
sap:Missing or Incorrect data after enabling Application Insights in Azure Portal

Troubleshoot OpenTelemetry issues in .NET

This article discusses how to troubleshoot OpenTelemetry issues in .NET.

Troubleshooting checklist

Step 1: Enable diagnostic logging

The Azure Monitor Exporter uses EventSource for its internal logging. The exporter logs are available to any EventListener by opting in to the source that's named OpenTelemetry-AzureMonitor-Exporter. For troubleshooting steps, see OpenTelemetry Troubleshooting on GitHub.

Step 2: Test connectivity between your application host and the ingestion service

Application Insights SDKs and agents send telemetry to get ingested as REST calls at our ingestion endpoints. To test connectivity from your web server or application host computer to the ingestion service endpoints, use cURL commands or raw REST requests from PowerShell. For more information, see Troubleshoot missing application telemetry in Azure Monitor Application Insights.

Known issues

The following items are known issues for the Azure Monitor OpenTelemetry Exporters:

  • The operation name is missing from dependency telemetry. The missing operation name causes failures and adversely affects performance tab experience.

  • The device model is missing from request and dependency telemetry. The missing device model adversely affects device cohort analysis.

[!INCLUDE Azure Help Support]