Skip to content

Commit e6f64f8

Browse files
trasktrask
committed
Acrolinx
1 parent fe96937 commit e6f64f8

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

‎articles/azure-monitor/app/java-standalone-upgrade-from-2x.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -11,25 +11,25 @@ ms.reviewer: mmcc
1111
# Upgrading from Application Insights Java 2.x SDK
1212

1313
There are typically no code changes when upgrading to 3.x. The 3.x SDK dependencies are just no-op API versions of the
14-
2.x SDK dependencies, but when used in conjunction with the 3.x Java agent, the 3.x Java agent provides the implementation
15-
for these 3.x SDK dependencies, so that any of your custom instrumentation will be correlated with all of the new
14+
2.x SDK dependencies, but when used along with the 3.x Java agent, the 3.x Java agent provides the implementation
15+
for them, and your custom instrumentation will be correlated with all the new
1616
auto-instrumentation which is provided by the 3.x Java agent.
1717

1818
## Step 1: Update dependencies
1919

20-
| 2.x dependency | Action | Remarks |
21-
|----------------|--------|---------|
22-
| `applicationinsights-core` | Update the version to `3.4.0` or later | |
23-
| `applicationinsights-web` | Update the version to `3.4.0` or later, and remove the Application Insights web filter your `web.xml` file. | |
24-
| `applicationinsights-web-auto` | Replace with `3.4.0` or later of `applicationinsights-web` | |
25-
| `applicationinsights-logging-log4j1_2` | Remove the dependency and remove the Application Insights appender from your log4j configuration. | This is no longer needed since Log4j 1.2 is auto-instrumented in the 3.x Java agent. |
26-
| `applicationinsights-logging-log4j2` | Remove the dependency and remove the Application Insights appender from your log4j configuration. | This is no longer needed since Log4j 2 is auto-instrumented in the 3.x Java agent. |
27-
| `applicationinsights-logging-log4j1_2` | Remove the dependency and remove the Application Insights appender from your logback configuration. | This is no longer needed since Logback is auto-instrumented in the 3.x Java agent. |
20+
| 2.x dependency | Action | Remarks |
21+
|----------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
22+
| `applicationinsights-core` | Update the version to `3.4.0` or later | |
23+
| `applicationinsights-web` | Update the version to `3.4.0` or later, and remove the Application Insights web filter your `web.xml` file. | |
24+
| `applicationinsights-web-auto` | Replace with `3.4.0` or later of `applicationinsights-web` | |
25+
| `applicationinsights-logging-log4j1_2` | Remove the dependency and remove the Application Insights appender from your log4j configuration. | No longer needed since Log4j 1.2 is auto-instrumented in the 3.x Java agent. |
26+
| `applicationinsights-logging-log4j2` | Remove the dependency and remove the Application Insights appender from your log4j configuration. | No longer needed since Log4j 2 is auto-instrumented in the 3.x Java agent. |
27+
| `applicationinsights-logging-log4j1_2` | Remove the dependency and remove the Application Insights appender from your logback configuration. | No longer needed since Logback is auto-instrumented in the 3.x Java agent. |
2828
| `applicationinsights-spring-boot-starter` | Replace with `3.4.0` or later of `applicationinsights-web` | The cloud role name will no longer default to `spring.application.name`, see the [3.x configuration docs](./java-standalone-config.md#cloud-role-name) for configuring the cloud role name. |
2929

3030
## Step 2: Add the 3.x Java agent
3131

32-
Add the 3.x Java agent to your JVM command-line args, e.g.
32+
Add the 3.x Java agent to your JVM command-line args, for example
3333

3434
```
3535
-javaagent:path/to/applicationinsights-agent-3.4.0.jar
@@ -64,12 +64,12 @@ This use case is supported in Application Insights Java 3.x using [Instrumentati
6464

6565
## Operation names
6666

67-
In the Application Insights Java 2.x SDK, in some cases, the operation names contained the full path, e.g.
67+
In the Application Insights Java 2.x SDK, in some cases, the operation names contained the full path, for example
6868

6969
:::image type="content" source="media/java-ipa/upgrade-from-2x/operation-names-with-full-path.png" alt-text="Screenshot showing operation names with full path":::
7070

7171
Operation names in Application Insights Java 3.x have changed to generally provide a better aggregated view
72-
in the Application Insights Portal U/X, e.g.
72+
in the Application Insights Portal U/X, for example
7373

7474
:::image type="content" source="media/java-ipa/upgrade-from-2x/operation-names-parameterized.png" alt-text="Screenshot showing operation names parameterized":::
7575

@@ -82,7 +82,7 @@ The snippet below configures 3 telemetry processors that combine to replicate th
8282
The telemetry processors perform the following actions (in order):
8383

8484
1. The first telemetry processor is an attribute processor (has type `attribute`),
85-
which means it applies to all telemetry which has attributes
85+
which means it applies to all telemetry that has attributes
8686
(currently `requests` and `dependencies`, but soon also `traces`).
8787

8888
It will match any telemetry that has attributes named `http.method` and `http.url`.

0 commit comments

Comments
 (0)