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/concept-manage-monitor-app-spring-boot-actuator.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ This configuration works with any Spring Boot version because versions are cover
49
49
By default, a Spring Boot application exposes the `health` endpoint only. To observe the configuration and configurable environment, use the following steps to enable the `env` and `configprops` endpoints as well:
50
50
51
51
1. Go to app **Overview** pane, select **Configuration** in the setting menu, and then go to the **Environment variables** configuration page.
52
-
1. Add the following properties as in the "key:value" form. This environment opens the following Spring Actuator endpoints: `health`, `env`, and `configprops`.
52
+
1. Add the following properties as in the `<key>:<value>` form. This environment opens the following Spring Actuator endpoints: `health`, `env`, and `configprops`.
Copy file name to clipboardExpand all lines: articles/spring-apps/basic-standard/github-actions-key-vault.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,11 +53,11 @@ Then save the results to GitHub **secrets** as described in [Set up your GitHub
53
53
54
54
The credential you created above can get only general information about the Key Vault, not the contents it stores. To get secrets stored in the Key Vault, you need set access policies for the credential.
55
55
56
-
Go to the **Key Vault** dashboard in Azure portal, select the **Access control** menu, then open the **Role assignments** tab. Select **Apps** for **Type** and `This resource` for **scope**. You should see the credential you created in previous step:
56
+
Go to the **Key Vault** dashboard in Azure portal, select the **Access control** menu, then open the **Role assignments** tab. Select **Apps** for **Type** and **This resource** for **scope**. You should see the credential you created in previous step:
57
57
58
58
:::image type="content" source="media/github-actions-key-vault/key-vault1.png" alt-text="Screenshot of the Azure portal that shows the Access control page with the Role assignments tab highlighted." lightbox="media/github-actions-key-vault/key-vault1.png":::
59
59
60
-
Copy the credential name, for example, `azure-cli-2020-01-19-04-39-02`. Open the **Access policies** menu, then select the **Add Access Policy** link. Select `Secret Management` for **Template**, then select **Principal**. Paste the credential name in **Principal**/**Select** input box:
60
+
Copy the credential name, for example, **azure-cli-2020-01-19-04-39-02**. Open the **Access policies** menu, then select the **Add Access Policy** link. Select **Secret Management** for **Template**, then select **Principal**. Paste the credential name in **Principal**/**Select** input box:
61
61
62
62
:::image type="content" source="media/github-actions-key-vault/key-vault2.png" alt-text="Screenshot of the Azure portal that shows the Add access policy page with the Principal pane open." lightbox="media/github-actions-key-vault/key-vault2.png":::
63
63
@@ -87,7 +87,7 @@ Again, results:
87
87
}
88
88
```
89
89
90
-
Copy the entire JSON string. Go back to **Key Vault** dashboard. Open the **Secrets** menu, then select the **Generate/Import** button. Input the secret name, such as `AZURE-CREDENTIALS-FOR-SPRING`. Paste the JSON credential string to the **Value** input box. You may notice the value input box is a one-line text field, rather than a multi-line text area. You can paste the complete JSON string there.
90
+
Copy the entire JSON string. Go back to **Key Vault** dashboard. Open the **Secrets** menu, then select the **Generate/Import** button. Input the secret name, such as **AZURE-CREDENTIALS-FOR-SPRING**. Paste the JSON credential string to the **Value** input box. You may notice the value input box is a one-line text field, rather than a multi-line text area. You can paste the complete JSON string there.
91
91
92
92
:::image type="content" source="media/github-actions-key-vault/key-vault3.png" alt-text="Screenshot of the Azure portal that shows the Create a secret page." lightbox="media/github-actions-key-vault/key-vault3.png":::
Copy file name to clipboardExpand all lines: articles/spring-apps/basic-standard/how-to-appdynamics-java-agent-monitor.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -220,7 +220,7 @@ You can define more metrics for the JVM, as shown in this screenshot of the **Me
220
220
221
221
## View AppDynamics Agent logs
222
222
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.
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:
Copy file name to clipboardExpand all lines: articles/spring-apps/basic-standard/how-to-application-insights.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ When the **Application Insights** feature is enabled, you can:
50
50
51
51
:::image type="content" source="media/how-to-application-insights/insights-process-agent-map.png" alt-text="Screenshot of the Azure portal that shows the Application Insights Application map page." lightbox="media/how-to-application-insights/insights-process-agent-map.png":::
52
52
53
-
* Select the link between customers-service and `petclinic` to see more details such as a query from SQL.
53
+
* Select the link between **customers-service** and **petclinic** to see more details such as a query from SQL.
54
54
* Select an endpoint to see all the applications making requests to the endpoint.
55
55
56
56
* In the navigation pane, select **Performance** to see the performance data of all applications' operations, dependencies, and roles.
@@ -74,7 +74,7 @@ When the **Application Insights** feature is enabled, you can:
74
74
75
75
:::image type="content" source="media/how-to-application-insights/petclinic-microservices-availability.png" alt-text="Screenshot of the Azure portal that shows the Application Insights Availability page." lightbox="media/how-to-application-insights/petclinic-microservices-availability.png":::
76
76
77
-
* In the navigation pane, select **Logs** to view all applications' logs, or one application's logs when filtering by `cloud_RoleName`.
77
+
* In the navigation pane, select **Logs** to view all applications' logs, or one application's logs when filtering by **cloud_RoleName**.
78
78
79
79
:::image type="content" source="media/how-to-application-insights/application-insights-application-logs.png" alt-text="Screenshot of the Azure portal that shows the Application Insights Logs page." lightbox="media/how-to-application-insights/application-insights-application-logs.png":::
|`terminationGracePeriodSeconds`| The duration in seconds after processes running in the app instance are sent a termination signal before they're forcibly halted. Set this value longer than the expected cleanup time for your process. The value must be a non-negative integer. Setting the grace period to **0** stops the app instance immediately via the kill signal, with no opportunity to shut down. If the value is **nil**, Azure Spring Apps uses the default grace period. The default value is **90**. |
57
+
|`terminationGracePeriodSeconds`| The duration in seconds after processes running in the app instance are sent a termination signal before they're forcibly halted. Set this value longer than the expected cleanup time for your process. The value must be a non-negative integer. Setting the grace period to `0` stops the app instance immediately via the kill signal, with no opportunity to shut down. If the value is `nil`, Azure Spring Apps uses the default grace period. The default value is `90`. |
58
58
59
59
### Health probe properties
60
60
61
61
The following table describes the properties you can use to configure health probes.
|`initialDelaySeconds`| The number of seconds after the app instance has started before probes are initiated. The default value is **0**, the minimum value. |
66
-
|`periodSeconds`| The frequency in seconds to perform the probe. The default value is **10**. The minimum value is **1**. |
67
-
|`timeoutSeconds`| The number of seconds until the probe times out. The default value is **1**, the minimum value. |
68
-
|`failureThreshold`| The minimum number of consecutive failures for the probe to be considered failed after having succeeded. The default value is **3**. The minimum value is **1**. |
69
-
|`successThreshold`| The minimum number of consecutive successes for the probe to be considered successful after having failed. The default value is **1**. The value must be **1** for liveness and startup. The minimum value is **1**. |
65
+
|`initialDelaySeconds`| The number of seconds after the app instance has started before probes are initiated. The default value is `0`, the minimum value. |
66
+
|`periodSeconds`| The frequency in seconds to perform the probe. The default value is `10`. The minimum value is `1`. |
67
+
|`timeoutSeconds`| The number of seconds until the probe times out. The default value is `1`, the minimum value. |
68
+
|`failureThreshold`| The minimum number of consecutive failures for the probe to be considered failed after having succeeded. The default value is `3`. The minimum value is `1`. |
69
+
|`successThreshold`| The minimum number of consecutive successes for the probe to be considered successful after having failed. The default value is `1`. The value must be `1` for liveness and startup. The minimum value is `1`. |
70
70
71
71
### Probe action properties
72
72
@@ -78,16 +78,16 @@ There are three ways you can check an app instance using a probe. Each probe mus
|`command`| The command to execute inside the app instance. The working directory for the command is the root directory (**/**) in the app instance's file system. Because the command is run using `exec` rather than inside a shell, shell instructions won't work. To use a shell, explicitly call out to the shell. An exit status of **0** is treated as live/healthy, and non-zero is unhealthy. |
90
+
|`command`| The command to execute inside the app instance. The working directory for the command is the root directory (**/**) in the app instance's file system. Because the command is run using `exec` rather than inside a shell, shell instructions won't work. To use a shell, explicitly call out to the shell. An exit status of `0` is treated as live/healthy, and non-zero is unhealthy. |
0 commit comments