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/container-apps/java-apm-agent-config.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.author: kuzhong
12
12
13
13
# Tutorial: Configure APM integration for Java applications with Java agent and init-container
14
14
15
-
APM (Application Performance Management) is useful when it comes to observability for your applications running online. You can package the APM plugin in the same image or Dockerfile with your app, but this will bind the management efforts together, like release and CVE (Common Vulnerabilities and Exposures) mitigation. Alternatively, you can leverage Java agent and init containers in Azure Container Apps to inject APM solutions without modifying your app image.
15
+
APM (Application Performance Management) is useful when it comes to observability for your applications running online. You can package the APM plugin in the same image or Dockerfile with your app, but it binds the management efforts together, like release and CVE (Common Vulnerabilities and Exposures) mitigation. Alternatively, you can apply Java agent and init containers in Azure Container Apps to inject APM solutions without modifying your app image.
16
16
17
17
In this tutorial, you learn how to:
18
18
@@ -195,7 +195,7 @@ The following commands help you define variables and ensure your Container Apps
195
195
--query "properties.provisioningState"
196
196
```
197
197
198
-
Once created, the command returns a "Succeeded" message.
198
+
Once created, the command returns a "Succeeded" message.
199
199
200
200
1. Create a Container app for further configurations.
201
201
@@ -219,9 +219,9 @@ The following commands help you define variables and ensure your Container Apps
219
219
--query "properties.provisioningState"
220
220
```
221
221
222
-
Once created, the command returns a "Succeeded" message.
222
+
Once created, the command returns a "Succeeded" message.
223
223
224
-
## Configure init-container, environment variables and volumes to set up Application Insights integration
224
+
## Configure init-container, environment variables, and volumes to set up Application Insights integration
225
225
226
226
1. Get current configurations of the running Container App.
227
227
@@ -243,11 +243,11 @@ The following commands help you define variables and ensure your Container Apps
243
243
-o yaml > app.yaml
244
244
```
245
245
246
-
YAML File `app.yaml` is created in current directory.
246
+
The YAML file `app.yaml` is created in current directory.
247
247
248
-
2. Edit the app YAML file.
248
+
1. Edit the app YAML file.
249
249
250
-
- Add a secret for Application Insights connection string
250
+
- Add secret for Application Insights connection string
251
251
252
252
```yaml
253
253
properties:
@@ -309,7 +309,7 @@ The following commands help you define variables and ensure your Container Apps
309
309
volumeName: java-agent-volume
310
310
```
311
311
312
-
3. Update the Container App with modified YAML file.
312
+
1. Update the Container App with modified YAML file.
313
313
314
314
# [Bash](#tab/bash)
315
315
@@ -331,11 +331,11 @@ The following commands help you define variables and ensure your Container Apps
331
331
--query "properties.provisioningState"
332
332
```
333
333
334
-
Once updated, the command returns a "Succeeded" message. Then you can check out your Application Insights in Azure portal to see your Container App is connected.
334
+
Once updated, the command returns a "Succeeded" message. Then you can check out your Application Insights in Azure portal to see your Container App is connected.
335
335
336
336
## Clean up resources
337
337
338
-
The resources created in this tutorial contributes to your Azure bill. If you are not going to keep them in a long run, run the following commands to clean them up.
338
+
The resources created in this tutorial contribute to your Azure bill. If you are not going to keep them in a long run, run the following commands to clean them up.
0 commit comments