Skip to content

Commit ea16114

Browse files
committed
Further improvements
1 parent 64af79b commit ea16114

File tree

2 files changed

+14
-10
lines changed

2 files changed

+14
-10
lines changed

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

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,9 @@ ms.reviewer: mmcc
1111

1212
# Enable Azure Monitor OpenTelemetry for .NET, Node.js, Python, and Java applications
1313

14-
This article describes how to enable and configure OpenTelemetry-based data collection within [Application Insights](app-insights-overview.md#application-insights-overview). The Azure Monitor OpenTelemetry Distro:
14+
This article describes how to enable and configure OpenTelemetry-based data collection within [Application Insights](app-insights-overview.md#application-insights-overview).
15+
16+
The Azure Monitor OpenTelemetry Distro:
1517

1618
* Provides an [OpenTelemetry distribution](https://opentelemetry.io/docs/concepts/distributions/#what-is-a-distribution) that includes support for features specific to Azure Monitor.
1719
* Enables [automatic](opentelemetry-add-modify.md#automatic-data-collection) telemetry by including OpenTelemetry instrumentation libraries for collecting traces, metrics, logs, and exceptions.
@@ -20,19 +22,16 @@ This article describes how to enable and configure OpenTelemetry-based data coll
2022

2123
For more information about the advantages of using the Azure Monitor OpenTelemetry Distro, see [Why should I use the "Azure Monitor OpenTelemetry Distro"?](#why-should-i-use-the-azure-monitor-opentelemetry-distro).
2224

23-
<!-- Will move to a different section:
2425
To learn more about collecting data using OpenTelemetry, see [Data Collection Basics](opentelemetry-overview.md) or [OpenTelemetry FAQ](#frequently-asked-questions).
25-
-->
2626

2727
## OpenTelemetry release status
2828

2929
OpenTelemetry offerings are available for .NET, Node.js, Python, and Java applications.
3030

3131
> [!NOTE]
3232
> * For a feature-by-feature release status, see the [FAQ](#whats-the-current-release-state-of-features-within-the-azure-monitor-opentelemetry-distro).
33-
> * The second tab of this article covers .NET scenarios, including classic ASP.NET, console apps, Windows Forms (WinForms), etc.
3433
35-
Follow the steps in this section to instrument your application with OpenTelemetry.
34+
3635

3736
## Prerequisites
3837

@@ -42,6 +41,13 @@ Follow the steps in this section to instrument your application with OpenTelemet
4241
4342
<!---NOTE TO CONTRIBUTORS: PLEASE DO NOT SEPARATE OUT JAVASCRIPT AND TYPESCRIPT INTO DIFFERENT TABS.--->
4443

44+
## Get started
45+
46+
Follow the steps in this section to instrument your application with OpenTelemetry. Select a tab for langauge-specific instructions.
47+
48+
> [!NOTE]
49+
> The .NET covers multiple scenarios, including classic ASP.NET, console apps, Windows Forms (WinForms), etc.
50+
4551
### [ASP.NET Core](#tab/aspnetcore)
4652

4753
> [!div class="checklist"]
@@ -74,9 +80,7 @@ Follow the steps in this section to instrument your application with OpenTelemet
7480
> If you rely on any properties in the [not-supported table](https://github.com/microsoft/ApplicationInsights-node.js/blob/beta/README.md#ApplicationInsights-Shim-Unsupported-Properties), use the distro, and we'll provide a migration guide soon. If not, the App Insights shim is your easiest path forward when it's out of beta.
7581
7682
> [!div class="checklist"]
77-
> * Application using an officially [supported version](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/monitor/monitor-opentelemetry-exporter#currently-supported-environments) of Node.js runtime:
78-
* [OpenTelemetry supported runtimes](https://github.com/open-telemetry/opentelemetry-js#supported-runtimes)
79-
* [Azure Monitor OpenTelemetry Exporter supported runtimes](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/monitor/monitor-opentelemetry-exporter#currently-supported-environments)
83+
> * Application using an officially [supported version](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/monitor/monitor-opentelemetry-exporter#currently-supported-environments) of Node.js runtime:<br>• [OpenTelemetry supported runtimes](https://github.com/open-telemetry/opentelemetry-js#supported-runtimes)<br>• [Azure Monitor OpenTelemetry Exporter supported runtimes](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/monitor/monitor-opentelemetry-exporter#currently-supported-environments)
8084
8185
> [!Tip]
8286
> If you're migrating from the Application Insights Classic API, see our [migration documentation](./opentelemetry-nodejs-migrate.md).

articles/azure-monitor/includes/azure-monitor-app-insights-opentelemetry-faqs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,11 +28,11 @@ Microsoft is investing in OpenTelemetry for the following reasons:
2828

2929
See [OpenTelemetry Status](https://opentelemetry.io/status/).
3030

31-
### What is the "Azure Monitor OpenTelemetry Distro"?
31+
### What is the Azure Monitor OpenTelemetry Distro?
3232

3333
You can think of it as a thin wrapper that bundles together all the OpenTelemetry components for a first class experience on Azure. This wrapper is also called a [distribution](https://opentelemetry.io/docs/concepts/distributions/) in OpenTelemetry.
3434

35-
### Why should I use the "Azure Monitor OpenTelemetry Distro"?
35+
### Why should I use the Azure Monitor OpenTelemetry Distro?
3636

3737
There are several advantages to using the Azure Monitor OpenTelemetry Distro over native OpenTelemetry from the community:
3838

0 commit comments

Comments
 (0)