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/spring-apps/basic-standard/how-to-appdynamics-java-agent-monitor.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "How to monitor Spring Boot apps with the AppDynamics Java Agent (Preview)"
3
3
titleSuffix: Azure Spring Apps
4
4
description: How to use the AppDynamics Java agent to monitor Spring Boot applications in Azure Spring Apps.
5
-
author: KarlErickson
5
+
author: KarlErickson
6
6
ms.author: jiec
7
7
ms.service: spring-apps
8
8
ms.topic: how-to
@@ -92,13 +92,13 @@ To activate an application through the Azure portal, use the following steps.
92
92
93
93
1. Select **Apps** in the **Settings** section of the navigation pane.
94
94
95
-
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/azure-spring-cloud-app-list.png" alt-text="Screenshot of the Azure portal showing the Apps page for an Azure Spring Apps instance." lightbox="media/how-to-appdynamics-java-agent-monitor/azure-spring-cloud-app-list.png":::
95
+
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/azure-spring-cloud-app-list.png" alt-text="Screenshot of the Azure portal that shows the Apps page for an Azure Spring Apps instance." lightbox="media/how-to-appdynamics-java-agent-monitor/azure-spring-cloud-app-list.png":::
96
96
97
97
1. Select the app, and then select **Configuration** in the navigation pane.
98
98
99
99
1. Use the **General settings** tab to update values such as the JVM options.
100
100
101
-
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/azure-spring-cloud-app-configuration-general.png" alt-text="Screenshot of the Azure portal showing the Configuration page for an app in an Azure Spring Apps instance, with the General settings tab selected." lightbox="media/how-to-appdynamics-java-agent-monitor/azure-spring-cloud-app-configuration-general.png":::
101
+
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/azure-spring-cloud-app-configuration-general.png" alt-text="Screenshot of the Azure portal that shows the Configuration page for an app in an Azure Spring Apps instance, with the General settings tab selected." lightbox="media/how-to-appdynamics-java-agent-monitor/azure-spring-cloud-app-configuration-general.png":::
102
102
103
103
1. Select **Environment variables** to add or update the variables used by your application.
104
104
@@ -180,47 +180,47 @@ This section shows various reports in AppDynamics.
180
180
181
181
The following screenshot shows an overview of your apps in the AppDynamics dashboard:
182
182
183
-
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-birds-eye-view-of-apps.jpg" alt-text="AppDynamics screenshot showing the Applications page." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-birds-eye-view-of-apps.jpg":::
183
+
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-birds-eye-view-of-apps.jpg" alt-text="Screenshot of AppDynamics that shows the Applications dashboard." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-birds-eye-view-of-apps.jpg":::
184
184
185
-
The **Application Dashboard** shows the overall information for each of your apps, as shown in the following screenshots using example applications:
185
+
The **Applications** tab shows the overall information for each of your apps, as shown in the following screenshots using example applications:
186
186
187
187
-`api-gateway`
188
188
189
-
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-api-gateway.jpg" alt-text="AppDynamics screenshot showing the Application Dashboard for the example api-gateway app." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-api-gateway.jpg":::
189
+
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-api-gateway.jpg" alt-text="Screenshot of AppDynamics that shows the Application dashboard for the example api-gateway app." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-api-gateway.jpg":::
190
190
191
191
-`customers-service`
192
192
193
-
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service.jpg" alt-text="AppDynamics screenshot showing the Application Dashboard for the example customers-service app." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service.jpg":::
193
+
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service.jpg" alt-text="Screenshot of AppDynamics that shows the Application dashboard for the example customers-service app." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service.jpg":::
194
194
195
195
The following screenshot shows how you can get basic information from the **Database Calls** dashboard.
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customer-service-db-calls.jpg" alt-text="Screenshot of AppDynamics that shows the Database Calls dashboard." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customer-service-db-calls.jpg":::
198
198
199
199
You can also get information about the slowest database calls, as shown in these screenshots:
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-slowest-db-calls-from-customers-service.jpg" alt-text="Screenshot of AppDynamics that shows the Slowest Database Calls page." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-slowest-db-calls-from-customers-service.jpg":::
202
202
203
-
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-slowest-db-calls-from-customers-service-2.jpg" alt-text="AppDynamics screenshot showing the Correlated Snapshots page accessed from the Slowest Database Calls page." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-slowest-db-calls-from-customers-service-2.jpg":::
203
+
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-slowest-db-calls-from-customers-service-2.jpg" alt-text="Screenshot of AppDynamics that shows the Correlated Snapshots page accessed from the Slowest Database Calls page." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-slowest-db-calls-from-customers-service-2.jpg":::
204
204
205
205
The following screenshot shows memory usage analysis in the **Heap** section of the **Memory** page:
206
206
207
-
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-memory-usage.jpg" alt-text="AppDynamics screenshot showing the Heap section of the Memory page." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-memory-usage.jpg":::
207
+
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-memory-usage.jpg" alt-text="Screenshot of AppDynamics that shows the Heap section of the Memory page." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-memory-usage.jpg":::
208
208
209
209
You can also see the garbage collection process, as shown in this screenshot:
210
210
211
-
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-garbage-collection.jpg" alt-text="AppDynamics screenshot showing the Garbage Collection section of the Memory page." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-garbage-collection.jpg":::
211
+
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-garbage-collection.jpg" alt-text="Screenshot of AppDynamics that shows the Garbage Collection section of the Memory page." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-garbage-collection.jpg":::
212
212
213
213
The following screenshot shows the **Slow Transactions** page:
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-slowest-transactions.jpg" alt-text="Screenshot of AppDynamics that shows the Slow Transactions page." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-slowest-transactions.jpg":::
216
216
217
217
You can define more metrics for the JVM, as shown in this screenshot of the **Metric Browser**:
218
218
219
-
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-jvm-metric-browser.jpg" alt-text="AppDynamics screenshot showing the Metric Browser." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-jvm-metric-browser.jpg":::
219
+
:::image type="content" source="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-jvm-metric-browser.jpg" alt-text="Screenshot of AppDynamics that shows the Metric Browser." lightbox="media/how-to-appdynamics-java-agent-monitor/appdynamics-dashboard-customers-service-jvm-metric-browser.jpg":::
220
220
221
221
## View AppDynamics Agent logs
222
222
223
-
By default, Azure Spring Apps will print the *info* level logs of the AppDynamics Agent to `STDOUT`. The logs will be mixed with the application logs. You can find the explicit agent version from the application logs.
223
+
By default, Azure Spring Apps prints the *info* level logs of the AppDynamics Agent to `STDOUT`. The logs are mixed with the application logs. You can find the explicit agent version from the application logs.
224
224
225
225
You can also get the logs of the AppDynamics Agent from the following locations:
226
226
@@ -230,14 +230,14 @@ You can also get the logs of the AppDynamics Agent from the following locations:
230
230
231
231
## Learn about AppDynamics Agent upgrade
232
232
233
-
The AppDynamics Agent will be upgraded regularly with JDK (quarterly). Agent upgrade may affect the following scenarios:
233
+
The AppDynamics Agent is upgraded regularly with JDK (quarterly). Agent upgrade might affect the following scenarios:
234
234
235
-
* Existing applications using AppDynamics Agent before upgrade will be unchanged, but will require restart or redeploy to engage the new version of AppDynamics Agent.
236
-
* Applications created after upgrade will use the new version of AppDynamics Agent.
235
+
- Existing applications using AppDynamics Agent before upgrade are unchanged, but require restart or redeploy to engage the new version of AppDynamics Agent.
236
+
- Applications created after upgrade use the new version of AppDynamics Agent.
For virtual network injection instances of Azure Spring Apps, make sure the outbound traffic is configured correctly for AppDynamics Agent. For details, see [SaaS Domains and IP Ranges](https://docs.appdynamics.com/appd/24.x/latest/en/cisco-appdynamics-essentials/getting-started/saas-domains-and-ip-ranges) and [Customer responsibilities for running Azure Spring Apps in a virtual network](../enterprise/vnet-customer-responsibilities.md?toc=/azure/spring-apps/basic-standard/toc.json&bc=/azure/spring-apps/basic-standard/breadcrumb/toc.json).
240
+
For virtual network injection instances of Azure Spring Apps, make sure the outbound traffic is configured correctly for AppDynamics Agent. For details, see [Cisco AppDynamics SaaS Domains and IP Ranges](https://docs.appdynamics.com/paa/en/cisco-appdynamics-saas-domains-and-ip-ranges) and [Customer responsibilities for running Azure Spring Apps in a virtual network](../enterprise/vnet-customer-responsibilities.md?toc=/azure/spring-apps/basic-standard/toc.json&bc=/azure/spring-apps/basic-standard/breadcrumb/toc.json).
Copy file name to clipboardExpand all lines: articles/spring-apps/enterprise/concept-app-status.md
+18-17Lines changed: 18 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn the app status categories in Azure Spring Apps
4
4
author: KarlErickson
5
5
ms.service: spring-apps
6
6
ms.topic: conceptual
7
-
ms.date: 03/30/2022
7
+
ms.date: 03/26/2024
8
8
ms.author: karler
9
9
ms.custom: devx-track-java
10
10
---
@@ -26,13 +26,13 @@ The Azure Spring Apps UI delivers information about the status of running applic
26
26
27
27
To view general status of an application type, select **Apps** in the left navigation pane of a resource group to display the following status information of the deployed app:
28
28
29
-
***Provisioning state**: Shows the deployment’s provisioning state.
29
+
***Provisioning state**: Shows the deployment's provisioning state.
30
30
***Running instance**: Shows how many app instances are running and how many app instances you desire. If you stop the app, this column shows **stopped**.
31
-
***Registered status**: Shows how many app instances are registered to Eureka and how many app instances you desire. If you stop the app, this column shows **stopped**. Eureka isn't applicable to the Enterprise plan. For more information if you're using the Enterprise plan, see [Use Service Registry](how-to-enterprise-service-registry.md).
31
+
***Registration status**: Shows how many app instances are registered in service discovery and how many app instances you desire. If you stop the app, this column shows **stopped**.
32
32
33
33
:::image type="content" source="media/concept-app-status/apps-ui-status.png" alt-text="Screenshot of the Azure portal that shows the Apps Settings page with specific columns highlighted." lightbox="media/concept-app-status/apps-ui-status.png":::
34
34
35
-
## Deployment status
35
+
###Deployment status
36
36
37
37
The deployment status shows the running state of the deployment. The status is reported as one of the following values:
38
38
@@ -41,26 +41,30 @@ The deployment status shows the running state of the deployment. The status is r
41
41
| Running | The deployment SHOULD be running. |
42
42
| Stopped | The deployment SHOULD be stopped. |
43
43
44
-
## Provisioning status
44
+
###Provisioning status
45
45
46
-
The *deployment provisioning* status describes the state of operations of the deployment resource. This status shows the comparison between the functionality and the deployment definition.
46
+
The deployment provisioning status describes the state of operations of the deployment resource. This status shows the comparison between the functionality and the deployment definition.
47
47
48
-
The provisioning state is accessible only from the CLI. It's reported as one of the following values:
48
+
The provisioning state is accessible only from the CLI. The status is reported as one of the following values:
| Creating | The resource is creating and isn't ready. |
53
-
| Updating | The resource is updating and the functionality may be different from the deployment definition until the update is complete. |
53
+
| Updating | The resource is updating and the functionality might be different from the deployment definition until the update is complete. |
54
54
| Succeeded | Successfully supplied resources and deploys the binary. The deployment's functionality is the same as the definition and all app instances are working. |
55
55
| Failed | Failed to achieve the *Succeeded* goal. |
56
56
| Deleting | The resource is being deleted which prevents operation, and the resource isn't available in this status. |
57
57
58
+
### Registration status
59
+
60
+
The app registration status shows the state in service discovery. The Basic/Standard plan uses Eureka for service discovery. For more information on how the Eureka client calculates the state, see [Eureka's health checks](https://cloud.spring.io/spring-cloud-static/Greenwich.RELEASE/multi/multi__service_discovery_eureka_clients.html#_eureka_s_health_checks). The Enterprise pricing plan uses [Tanzu Service Registry](how-to-enterprise-service-registry.md) for service discovery.
61
+
58
62
## App instances status
59
63
60
-
The *app instance* status represents every instance of the app. To view the status of a specific instance of a deployed app, select the **App instance** pane and then select the **App Instance Name** value for the app. The following status values will appear:
64
+
The *app instance* status represents every instance of the app. To view the status of a specific instance of a deployed app, select the **App instance** pane and then select the **App Instance Name** value for the app. The following status values appear:
61
65
62
-
***Status**: Whether the instance is runningor its current state
63
-
***Discovery Status**: The registered status of the app instance in the Eureka server
66
+
***Status**: Indicates whether the instance is starting, running, terminating, or in failed state.
67
+
***Discovery Status**: The registered status of the app instance in the Eureka server or the Service Registry.
64
68
65
69
:::image type="content" source="media/concept-app-status/apps-ui-instance-status.png" alt-text="Screenshot of the Azure portal showing the App instance Settings page with the Status and Discovery status columns highlighted." lightbox="media/concept-app-status/apps-ui-instance-status.png":::
66
70
@@ -70,10 +74,10 @@ The instance status is reported as one of the following values:
70
74
71
75
| Value | Definition |
72
76
|-------------|------------|
73
-
| Starting | The binary is successfully deployed to the given instance. The instance booting the jar file may fail because the jar can't run properly. Azure Spring Apps will restart the app instance in 60 seconds if it detects that the app instance is still in the *Starting* state. |
77
+
| Starting | The binary is successfully deployed to the given instance. The instance booting the jar file might fail because the jar can't run properly. Azure Spring Apps restarts the app instance in 60 seconds if it detects that the app instance is still in the *Starting* state. |
74
78
| Running | The instance works. The instance can serve requests from inside Azure Spring Apps. |
75
-
| Failed | The app instance failed to start the user’s binary after several retries. The app instance may be in one of the following states:<br/>- The app may stay in the *Starting* status and never be ready for serving requests.<br/>- The app may boot up but crashed in a few seconds. |
76
-
| Terminating | The app instance is shutting down. The app may not serve requests and the app instance will be removed. |
79
+
| Failed | The app instance failed to start the user's binary after several retries. The app instance might be in one of the following states:<br/>- The app might stay in the *Starting* status and never be ready for serving requests.<br/>- The app might boot up but crash in a few seconds. |
80
+
| Terminating | The app instance is shutting down. The app might not serve requests and the app instance is removed. |
77
81
78
82
### App discovery status
79
83
@@ -87,9 +91,6 @@ The discovery status of the instance is reported as one of the following values:
87
91
| UNREGISTERED | The app instance isn't registered to Eureka. |
88
92
| N/A | The app instance is running with custom container or service discovery is not enabled. |
89
93
90
-
## App registration status
91
-
92
-
The app registration status shows the state in service discovery. Azure Spring Apps uses Eureka for service discovery. For more information on how the Eureka client calculates the state, see [Eureka's health checks](https://cloud.spring.io/spring-cloud-static/Greenwich.RELEASE/multi/multi__service_discovery_eureka_clients.html#_eureka_s_health_checks).
93
94
## Next steps
94
95
95
96
*[Prepare a Spring or Steeltoe application for deployment in Azure Spring Apps](how-to-prepare-app-deployment.md)
0 commit comments