Skip to content

Commit 68411e3

Browse files
Merge pull request #215526 from AaronMaxwell/aaronmax-otel-enable-update1
OTel weekend Update 1
2 parents 4615879 + 9594a1d commit 68411e3

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/azure-monitor/app/opentelemetry-enable.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.reviewer: mmcc
99

1010
# Enable Azure Monitor OpenTelemetry for .NET, Node.js, and Python applications (preview)
1111

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).
1313

1414
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.
1515

@@ -35,7 +35,7 @@ Consider whether this preview is right for you. It *enables distributed tracing,
3535
- Ability to manually set User ID or Authenticated User ID
3636
- Propagating Operation Name to Dependency Telemetry
3737
- [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.
3939

4040
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.
4141

@@ -303,7 +303,7 @@ Run your application and open your **Application Insights Resource** tab in the
303303
> [!IMPORTANT]
304304
> 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.
305305
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).
307307

308308
## Set the Cloud Role Name and the Cloud Role Instance
309309

@@ -1276,8 +1276,8 @@ input()
12761276

12771277
Select instrumentation libraries automatically support exceptions to Application Insights.
12781278
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.
12811281

12821282
#### [.NET](#tab/net)
12831283

@@ -1606,7 +1606,7 @@ To provide feedback:
16061606
### [Node.js](#tab/nodejs)
16071607

16081608
- To review the source code, see the [Azure Monitor Exporter GitHub repository](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/monitor/monitor-opentelemetry-exporter).
1609-
- To install the NPM package, check for updates, or view release notes, see the [Azure Monitor Exporter NPM Package](https://www.npmjs.com/package/@azure/monitor-opentelemetry-exporter) page.
1609+
- To install the npm package, check for updates, or view release notes, see the [Azure Monitor Exporter npm Package](https://www.npmjs.com/package/@azure/monitor-opentelemetry-exporter) page.
16101610
- To become more familiar with Azure Monitor Application Insights and OpenTelemetry, see the [Azure Monitor Example Application](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/monitor/monitor-opentelemetry-exporter/samples).
16111611
- To learn more about OpenTelemetry and its community, see the [OpenTelemetry JavaScript GitHub repository](https://github.com/open-telemetry/opentelemetry-js).
16121612
- To enable usage experiences, [enable web or browser user monitoring](javascript.md).

0 commit comments

Comments
 (0)