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/java-in-process-agent.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ Add `-javaagent:"path/to/applicationinsights-agent-3.3.1.jar"` to your applicati
71
71
- You can set an environment variable:
72
72
73
73
```console
74
-
APPLICATIONINSIGHTS_CONNECTION_STRING = <Copy connection string from Application Insights Resource Overview>
74
+
APPLICATIONINSIGHTS_CONNECTION_STRING=<Copy connection string from Application Insights Resource Overview>
75
75
```
76
76
77
77
- Or you can create a configuration file named `applicationinsights.json`. Place it in the same directory as `applicationinsights-agent-3.3.1.jar` with the following content:
@@ -118,9 +118,9 @@ In the `applicationinsights.json` file, you can also configure these settings:
118
118
119
119
For more information, see [Configuration options](./java-standalone-config.md).
120
120
121
-
## Instrumentation libraries
121
+
## Automatic instrumentation
122
122
123
-
Java 3.x includes the following instrumentation libraries.
123
+
Java 3.x includes the following automatic instrumentation.
124
124
125
125
### Autocollected requests
126
126
@@ -225,7 +225,8 @@ This section explains how to modify telemetry.
225
225
226
226
### Add spans
227
227
228
-
You can use `opentelemetry-api` to create [tracers](https://opentelemetry.io/docs/instrumentation/java/manual/#tracing) and spans. Spans populate the dependencies table in Application Insights. The string passed in for the span's name is saved to the _target_ field within the dependency.
228
+
You can use `opentelemetry-api` to create [tracers](https://opentelemetry.io/docs/instrumentation/java/manual/#tracing) and spans.
229
+
Spans populate the `requests` and `dependencies` tables in Application Insights.
229
230
230
231
> [!NOTE]
231
232
> This feature is only in 3.2.0 and later.
@@ -287,9 +288,7 @@ You can use `opentelemetry-api` to create span events, which populate the traces
287
288
288
289
You can use `opentelemetry-api` to add attributes to spans. These attributes can include adding a custom business dimension to your telemetry. You can also use attributes to set optional fields in the Application Insights schema, such as User ID or Client IP.
289
290
290
-
#### Add a custom dimension
291
-
292
-
Adding one or more custom dimensions populates the _customDimensions_ field in the requests, dependencies, traces, or exceptions table.
291
+
Adding one or more span attributes populates the _customDimensions_ field in the requests, dependencies, traces, or exceptions table.
293
292
294
293
> [!NOTE]
295
294
> This feature is only in 3.2.0 and later.
@@ -409,8 +408,8 @@ The following table represents currently supported custom telemetry types that y
409
408
410
409
- Custom metrics are supported through micrometer.
411
410
- Custom exceptions and traces are supported through logging frameworks.
412
-
- Custom requests, dependencies, and exceptions are supported through `opentelemetry-api`.
413
-
-Any type of the custom telemetry is supported through the [Application Insights Java 2.x SDK](#send-custom-telemetry-by-using-the-2x-sdk).
411
+
- Custom requests, dependencies, metrics, and exceptions are supported through `opentelemetry-api`.
412
+
-All types of the custom telemetry is supported through the [Application Insights Java 2.x SDK](#send-custom-telemetry-by-using-the-2x-sdk).
0 commit comments