You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/opentelemetry-enable.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.reviewer: mmcc
9
9
10
10
# Enable Azure Monitor OpenTelemetry for .NET, Node.js, and Python applications (preview)
11
11
12
-
The Azure Monitor OpenTelemetry Exporter is a component that sends traces (and eventually all application telemetry) to Azure Monitor Application Insights. To learn more about OpenTelemetry concepts, see the [OpenTelemetry overview](opentelemetry-overview.md) or [OpenTelemetry FAQ](/azure/azure-monitor/faq#opentelemetry).
12
+
The Azure Monitor OpenTelemetry Exporter is a component that sends traces, and metrics (and eventually all application telemetry) to Azure Monitor Application Insights. To learn more about OpenTelemetry concepts, see the [OpenTelemetry overview](opentelemetry-overview.md) or [OpenTelemetry FAQ](/azure/azure-monitor/faq#opentelemetry).
13
13
14
14
This article describes how to enable and configure the OpenTelemetry-based Azure Monitor Preview offerings. After you finish the instructions in this article, you'll be able to send OpenTelemetry traces and metrics to Azure Monitor Application Insights.
15
15
@@ -35,7 +35,7 @@ Consider whether this preview is right for you. It *enables distributed tracing,
35
35
- Ability to manually set User ID or Authenticated User ID
36
36
- Propagating Operation Name to Dependency Telemetry
37
37
-[Instrumentation libraries](#instrumentation-libraries) support on Azure Functions
38
-
-[Status](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#set-status)only supports statuscode(unset,ok,error) and status-description. "Status Description" is ignored by Azure Monitor Exporters.
38
+
-[Status](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#set-status) supports statuscode(unset,ok,error) and status-description. "Status Description" is ignored by Azure Monitor Exporters.
39
39
40
40
If you require a full-feature experience, use the existing Application Insights [ASP.NET](asp-net.md), or [ASP.NET Core](asp-net-core.md) SDK until the OpenTelemetry-based offering matures.
41
41
@@ -303,7 +303,7 @@ Run your application and open your **Application Insights Resource** tab in the
303
303
> [!IMPORTANT]
304
304
> If you have two or more services that emit telemetry to the same Application Insights resource, you're required to [set Cloud Role Names](#set-the-cloud-role-name-and-the-cloud-role-instance) to represent them properly on the Application Map.
305
305
306
-
As part of using Application Insights instrumentation, we collect and send diagnostic data to Microsoft. This data helps us run and improve Application Insights. You have the option to disable nonessential data collection. To learn more, see [Statsbeat in Azure Application Insights](./statsbeat.md).
306
+
As part of using Application Insights instrumentation, we collect and send diagnostic data to Microsoft. This data helps us run and improve Application Insights. You may disable nonessential data collection. To learn more, see [Statsbeat in Azure Application Insights](./statsbeat.md).
307
307
308
308
## Set the Cloud Role Name and the Cloud Role Instance
309
309
@@ -1276,8 +1276,8 @@ input()
1276
1276
1277
1277
Select instrumentation libraries automatically support exceptions to Application Insights.
1278
1278
However, you may want to manually report exceptions beyond what instrumentation libraries report.
1279
-
For instance, exceptions caught by your code *aren't* ordinarily not reported, and you may wish to report them
1280
-
and thus draw attention to them in relevant experiences including the failures blade and end-to-end transaction view.
1279
+
For instance, exceptions caught by your code aren't* ordinarily reported. You may wish to report them
1280
+
to draw attention in relevant experiences including the failures section and end-to-end transaction views.
0 commit comments