Skip to content

Commit 07dff78

Browse files
committed
Removing duplicate instances of instrumentation key note and making small edits
1 parent 0bf3adf commit 07dff78

File tree

1 file changed

+5
-11
lines changed

1 file changed

+5
-11
lines changed

articles/azure-monitor/app/deprecated-java-2x.md

Lines changed: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Azure Monitor Application Insights for Java 2.x
33
description: A step by step guide on using Java 2.x with Application Insights.
44
ms.topic: conceptual
5-
ms.date: 12/06/2022
5+
ms.date: 12/07/2022
66
ms.devlang: java
77
ms.custom: devx-track-java
88
ms.reviewer: mmcc
@@ -24,6 +24,8 @@ In this article, you'll learn how to use Java 2.x with Application Insights. Thi
2424
- Explore Linux system performance metrics in Application Insights by using collectd
2525
- Measure metrics for JVM-based application code and export the data to your favorite monitoring systems by using Micrometer application monitoring
2626

27+
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
28+
2729
## Get started with Application Insights in a Java web project
2830

2931
In this section, you use the Application Insights SDK to instrument request, track dependencies, and collect performance counters, diagnose performance issues and exceptions, and write code to track what users do with your app.
@@ -44,8 +46,6 @@ Application Insights is an extensible analytics service for web developers that
4446

4547
:::image type="content" source="./media/deprecated-java-2x/instrumentation-key-001.png" alt-text="In the new resource overview, click Properties and copy the Instrumentation Key." lightbox="./media/deprecated-java-2x/instrumentation-key-001.png":::
4648

47-
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
48-
4949
### Add the Application Insights SDK for Java to your project
5050

5151
*Choose your project type.*
@@ -133,7 +133,7 @@ Optionally, the configuration file can be in any location accessible to your app
133133
* The HTTP Request component is optional. It automatically sends telemetry about requests and response times to the portal.
134134
* Event correlation is an addition to the HTTP request component. It assigns an identifier to each request received by the server. It then adds this identifier as a property to every item of telemetry as the property 'Operation.Id'. It allows you to correlate the telemetry associated with each request by setting a filter in [diagnostic search][diagnostic].
135135

136-
### Alternative ways to set the instrumentation key
136+
#### Alternative ways to set the instrumentation key
137137
Application Insights SDK looks for the key in this order:
138138

139139
1. System property: -DAPPINSIGHTS_INSTRUMENTATIONKEY=your_ikey
@@ -309,8 +309,6 @@ If you're using Logback or Log4J (v1.2 or v2.0) for tracing, you can have your t
309309
> [!TIP]
310310
> You only need to set your Application Insights Instrumentation Key once for your application. If you are using a framework like Java Spring, you may have already registered the key elsewhere in your app's configuration.
311311
312-
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
313-
314312
### Using the Application Insights Java agent
315313

316314
By default, the Application Insights Java agent automatically captures logging performed at `WARN` level and above.
@@ -865,8 +863,6 @@ Take a copy of the instrumentation key, which identifies the resource.
865863

866864
:::image type="content" source="./media/deprecated-java-2x/instrumentation-key-001.png" alt-text="Browse all, open your resource, and then in the Essentials drop-down, select, and copy the Instrumentation Key" lightbox="./media/deprecated-java-2x/instrumentation-key-001.png":::
867865

868-
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
869-
870866
### Install collectd and the plug-in
871867
On your Linux server machines:
872868

@@ -1005,8 +1001,6 @@ Steps
10051001
1. Build your application and run
10061002
2. The above should get you up and running with pre-aggregated metrics auto collected to Azure Monitor.
10071003

1008-
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
1009-
10101004
### Using Spring 2.x
10111005

10121006
Add the following dependencies to your pom.xml or build.gradle file:
@@ -1227,11 +1221,11 @@ Add the following binding code to the configuration file:
12271221
* Add [monitoring to your web pages](javascript.md) to monitor page load times, AJAX calls, browser exceptions.
12281222
* Write [custom telemetry](./api-custom-events-metrics.md) to track usage in the browser or at the server.
12291223
* Use [Analytics](../logs/log-query-overview.md) for powerful queries over telemetry from your app
1230-
* For more information, visit [Azure for Java developers](/java/azure).
12311224
* [Diagnostic search][diagnostic]
12321225
* [Sampling](./sampling.md) - Consider sampling as an alternative to filtering that does not skew your metrics.
12331226
* To learn more about Micrometer, see the official [Micrometer documentation](https://micrometer.io/docs).
12341227
* To learn about Spring on Azure, see the official [Spring on Azure documentation](/java/azure/spring-framework/).
1228+
* For more information, visit [Azure for Java developers](/java/azure).
12351229

12361230
<!--Link references-->
12371231
[api]: ./api-custom-events-metrics.md

0 commit comments

Comments
 (0)