Skip to content

Commit db1ceda

Browse files
committed
edits
1 parent b07e112 commit db1ceda

File tree

2 files changed

+19
-19
lines changed

2 files changed

+19
-19
lines changed

articles/spring-apps/how-to-configure-enterprise-spring-cloud-gateway.md

Lines changed: 18 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -152,40 +152,42 @@ The following table describes the default resource usage:
152152
| VMware Spring Cloud Gateway | 2 | 1 core | 2Gi |
153153
| VMware Spring Cloud Gateway operator | 2 | 1 core | 2Gi |
154154

155-
## Configure Application Performance Monitoring
155+
## Configure application performance monitoring
156156

157-
There are several types of Application Performance Monitoring (APM) Java agents provided by Spring Cloud Gateway to monitor gateway managed by Azure Spring Apps. Use the two configurations to setup APM for Spring Cloud Gateway.
157+
There are several types of application performance monitoring (APM) Java agents provided by Spring Cloud Gateway to monitor a gateway managed by Azure Spring Apps.
158158

159-
#### [Portal](#tab/Azure-portal)
159+
### [Azure portal](#tab/Azure-portal)
160160

161-
The following steps are to set up APM using the Azure portal.
161+
Use the following steps to set up APM using the Azure portal:
162162

163-
1. Open the **Spring Cloud Gateway** page and select **Configuration** tabs.
163+
1. Open the **Spring Cloud Gateway** page and select the **Configuration** tab.
164164

165-
1. Choose the APM type to monitor gateway in the dropdown list of **APM**.
165+
1. Choose the APM type in the **APM** list to monitor a gateway.
166166

167-
1. Fill the key-value pairs environment variables of APM in the **Properties** or **Secrets**. You can put variables with sensitive information in **Secrets**.
167+
1. Fill in the key-value pairs for the APM environment variables in the **Properties** or **Secrets** sections. You can put variables with sensitive information in **Secrets**.
168168

169-
1. When all configurations provided, select **Save** at the bottom to save your changes.
169+
1. When you've provided all the configurations, select **Save** to save your changes.
170170

171171
Updating the configuration can take a few minutes. You should get a notification when the configuration is complete.
172172

173-
#### [CLI](#tab/Azure-CLI)
173+
### [Azure CLI](#tab/Azure-CLI)
174174

175-
The following steps use the Azure CLI to set up APM.
176-
177-
Run the following command
175+
Use the following command to set up APM using Azure CLI:
178176

179177
```azurecli
180-
az spring gateway update --apm-types <APM_TYPE> --properties <key=value> --secrets <key=value>
178+
az spring gateway update \
179+
--apm-types <APM-type> \
180+
--properties <key=value> \
181+
--secrets <key=value>
181182
```
182183

184+
---
183185

184-
The supported APM types are `ApplicationInsights`, `AppDynamics`, `Dynatrace`, `NewRelic` and `ElasticAPM`. You can refer to their public documents about APM Java agent to see full functions provided and which environment variables are exposed. Azure Spring Apps will upgrade APM agent in the same cadence as deployed apps to keep compatibility of agents between Spring Cloud Gateway and apps.
186+
The supported APM types are `ApplicationInsights`, `AppDynamics`, `Dynatrace`, `NewRelic`, and `ElasticAPM`. For more information about the functions provided and which environment variables are exposed, see the public documentation for the APM Java agent you're using. Azure Spring Apps will upgrade the APM agent with the same cadence as deployed apps to keep compatibility of agents between Spring Cloud Gateway and apps.
185187

186188
> [!NOTE]
187-
> By default, Azure Spring Apps prints the logs of the APM Java agent to `STDOUT`, which are mixed with Spring Cloud Gateway logs. You can check the version of APM agent used in logs. These logs can be queried in Log Analystics for troubleshooting.
188-
> Increase the cpu and memory of Spring Cloud Gateway to make APM agents work correctly.
189+
> By default, Azure Spring Apps prints the logs of the APM Java agent to `STDOUT`. These logs are mixed with the Spring Cloud Gateway logs. You can check the version of the APM agent used in the logs. You can query these logs in Log Analytics to troubleshoot.
190+
> To make the APM agents work correctly, increase the CPU and memory of Spring Cloud Gateway.
189191
190192
## Next steps
191193

articles/spring-apps/toc.yml

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -132,10 +132,8 @@ items:
132132
items:
133133
- name: Manage Spring Cloud Gateway
134134
href: how-to-configure-enterprise-spring-cloud-gateway.md
135-
- name: Configure Routes
135+
- name: Configure routes
136136
href: how-to-use-enterprise-spring-cloud-gateway.md
137-
- name: Debug your apps remotely
138-
href: how-to-remote-debugging-app-instance.md
139137
- name: Use VMware Tanzu Application Accelerator
140138
href: how-to-use-accelerator.md
141139
- name: Use Tanzu Application Platform GUI tools

0 commit comments

Comments
 (0)