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/opentelemetry-add-modify.md
+259-1Lines changed: 259 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,6 +138,28 @@ Telemetry emitted by these Azure SDKs is automatically collected by default:
138
138
[//]: #"}"
139
139
[//]: #"console.log(str)"
140
140
141
+
142
+
#### [Java Native](#tab/java-native)
143
+
144
+
Requests for Spring Boot native applications
145
+
* Spring Web
146
+
* Spring Web MVC
147
+
* Spring WebFlux
148
+
149
+
Dependencies for Spring Boot native applications
150
+
* JDBC
151
+
* R2DBC
152
+
* MongoDB
153
+
* Kafka
154
+
155
+
Metrics
156
+
* Micrometer Metrics
157
+
158
+
Logs for Spring Boot native applications
159
+
* Logback
160
+
161
+
For Quartz native applications, please look at the [Quarkus documentation](https://quarkus.io/guides/opentelemetry).
162
+
141
163
#### [Node.js](#tab/nodejs)
142
164
143
165
The following OpenTelemetry Instrumentation libraries are included as part of the Azure Monitor Application Insights Distro. For more information, see [Azure SDK for JavaScript](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/monitor/monitor-opentelemetry/README.md#instrumentation-libraries).
@@ -278,6 +300,10 @@ var metricsProvider = Sdk.CreateMeterProviderBuilder()
278
300
### [Java](#tab/java)
279
301
You can't extend the Java Distro with community instrumentation libraries. To request that we include another instrumentation library, open an issue on our GitHub page. You can find a link to our GitHub page in [Next Steps](#next-steps).
280
302
303
+
### [Java Native](#tab/java-native)
304
+
305
+
You can't use commmunity instrumentation libraries with GraalVM Java native applications.
306
+
281
307
### [Node.js](#tab/nodejs)
282
308
283
309
Other OpenTelemetry Instrumentations are available [here](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node) and could be added using TraceHandler in ApplicationInsightsClient.
1. Create a span, make it current, and then end it:
1256
1442
1257
1443
```java
@@ -1374,6 +1560,18 @@ You can use `opentelemetry-api` to create span events, which populate the `trace
1374
1560
Span.current().addEvent("eventName");
1375
1561
```
1376
1562
1563
+
#### [Java Native](#tab/java-native)
1564
+
1565
+
You can use OpenTelemetry API to create span events, which populate the `traces` table in Application Insights. The string passed in to `addEvent()` is saved to the `message` field within the trace.
-Toenableusageexperiences, see [Enableweborbrowserusermonitoring](javascript.md).
2370
2621
-Seethe [releasenotes](https://github.com/microsoft/ApplicationInsights-Java/releases) on GitHub.
2371
2622
2623
+
### [Java Native](#tab/java-native)
2624
+
-FordetailsonaddingandmodifyingAzureMonitorOpenTelemetry, see [AddandmodifyAzureMonitorOpenTelemetry](opentelemetry-add-modify.md).
2625
+
-Toreviewthesourcecode, see [AzureMonitorOpenTelemetryDistroinSpringBootnativeimageJavaapplication](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/spring/spring-cloud-azure-starter-monitor)
2626
+
and [QuarkusOpenTelemetryExporterforAzure](https://github.com/quarkiverse/quarkus-opentelemetry-exporter/tree/main/quarkus-opentelemetry-exporter-azure).
0 commit comments