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/quickstart-deploy-apps.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -224,7 +224,7 @@ Use the following steps to create and deploys apps on Azure Spring Apps using th
224
224
az configure --defaults group=<resource-group-name> spring=<service-name>
225
225
```
226
226
227
-
1. Create the two core Spring applications for PetClinic: API gateway and customers-service.
227
+
1. Create the two core Spring applications for PetClinic: `api-gateway` and `customers-service`.
228
228
229
229
```azurecli
230
230
az spring app create \
@@ -270,12 +270,12 @@ Use the following steps to create and deploys apps on Azure Spring Apps using th
270
270
271
271
## Verify the services
272
272
273
-
Access the app gateway and customersservice from browser with the **Public Url** shown previously, in the format of `https://<service name>-api-gateway.azuremicroservices.io`.
273
+
Access `api-gateway` and `customers-service` from a browser with the **Public Url** shown previously, in the format of `https://<service name>-api-gateway.azuremicroservices.io`.
274
274
275
275
:::image type="content" source="media/quickstart-deploy-apps/access-customers-service.png" alt-text="Screenshot of the PetClinic customers service." lightbox="media/quickstart-deploy-apps/access-customers-service.png":::
276
276
277
277
> [!TIP]
278
-
> To troubleshot deployments, you can use the following command to get logs streaming in real time whenever the app is running `az spring app logs --name <app name> -f`.
278
+
> To troubleshot deployments, you can use the following command to get logs streaming in real time whenever the app is running `az spring app logs --name <app name> --follow`.
279
279
280
280
## Deploy extra apps
281
281
@@ -431,7 +431,7 @@ To deploy to Azure, you must sign in with your Azure account with Azure Toolkit
431
431
:::image type="content" source="media/quickstart-deploy-apps/memory-jvm-options.png" alt-text="Screenshot of memory and JVM options." lightbox="media/quickstart-deploy-apps/memory-jvm-options.png":::
432
432
433
433
1. In the **Before launch** section of the dialog, double-click **Run Maven Goal**.
434
-
1. In the **Working directory** textbox, navigate to the *spring-petclinic-microservices/gateway* folder.
434
+
1. In the **Working directory** textbox, navigate to the *spring-petclinic-microservices/spring-petclinic-api-gateway* folder.
435
435
1. In the **Command line** textbox, enter *package -DskipTests*. Select **OK**.
436
436
437
437
:::image type="content" source="media/quickstart-deploy-apps/deploy-to-azure-spring-apps-2-pet-clinic.png" alt-text="Screenshot of the spring-petclinic-microservices/gateway page and command line textbox." lightbox="media/quickstart-deploy-apps/deploy-to-azure-spring-apps-2-pet-clinic.png":::
> Azure Spring Apps is the new name for the Azure Spring Cloud service. Although the service has a new name, you'll see the old name in some places for a while as we work to update assets such as screenshots, videos, and diagrams.
@@ -71,7 +71,7 @@ Executing ObjectResult, writing value of type 'System.Collections.Generic.KeyVal
71
71
72
72
1. Edit the query to remove the Where clauses that limit the display to warning and error logs.
73
73
74
-
1.Then select **Run**, and you'll see logs. For more information, see [Get started with log queries in Azure Monitor](../azure-monitor/logs/get-started-queries.md).
74
+
1.Select **Run**. You're shown logs. For more information, see [Get started with log queries in Azure Monitor](../azure-monitor/logs/get-started-queries.md).
75
75
76
76
:::image type="content" source="media/quickstart-logs-metrics-tracing/logs-query-steeltoe.png" alt-text="Screenshot of a Logs Analytics query." lightbox="media/quickstart-logs-metrics-tracing/logs-query-steeltoe.png":::
77
77
@@ -135,10 +135,14 @@ There are two ways to see logs on Azure Spring Apps: **Log Streaming** of real-t
135
135
You can use log streaming in the Azure CLI with the following command.
136
136
137
137
```azurecli
138
-
az spring app logs -s <service instance name> -g <resource group name> -n gateway -f
138
+
az spring app logs \
139
+
--resource-group <resource-group-name> \
140
+
--service <service-instance-name> \
141
+
--name api-gateway \
142
+
--follow
139
143
```
140
144
141
-
You'll see logs like this:
145
+
You're shown logs like this:
142
146
143
147
:::image type="content" source="media/quickstart-logs-metrics-tracing/logs-streaming-cli.png" alt-text="Screenshot of CLI log output." lightbox="media/quickstart-logs-metrics-tracing/logs-streaming-cli.png":::
144
148
@@ -163,7 +167,7 @@ To get the logs using Azure Toolkit for IntelliJ:
@@ -177,7 +181,7 @@ To get the logs using Azure Toolkit for IntelliJ:
177
181
178
182
:::image type="content" source="media/quickstart-logs-metrics-tracing/logs-entry.png" alt-text="Screenshot of the Logs opening page." lightbox="media/quickstart-logs-metrics-tracing/logs-entry.png":::
179
183
180
-
1. Then you'll see filtered logs. For more information, see [Get started with log queries in Azure Monitor](../azure-monitor/logs/get-started-queries.md).
184
+
1. Then you're shown filtered logs. For more information, see [Get started with log queries in Azure Monitor](../azure-monitor/logs/get-started-queries.md).
181
185
182
186
:::image type="content" source="media/quickstart-logs-metrics-tracing/logs-query.png" alt-text="Screenshot of filtered logs." lightbox="media/quickstart-logs-metrics-tracing/logs-query.png":::
183
187
@@ -189,16 +193,16 @@ The following chart shows `gateway-requests` (Spring Cloud Gateway), `hikaricp_c
189
193
190
194
:::image type="content" source="media/quickstart-logs-metrics-tracing/petclinic-microservices-metrics.jpg" alt-text="Screenshot of gateway requests." lightbox="media/quickstart-logs-metrics-tracing/petclinic-microservices-metrics.jpg":::
191
195
192
-
Spring Boot registers several core metrics, including JVM, CPU, Tomcat, and Logback. The Spring Boot auto-configuration enables the instrumentation of requests handled by Spring MVC. All three REST controllers (`OwnerResource`, `PetResource`, and `VisitResource`) have been instrumented by the `@Timed` Micrometer annotation at the class level.
196
+
Spring Boot registers several core metrics, including JVM, CPU, Tomcat, and Logback. The Spring Boot autoconfiguration enables the instrumentation of requests handled by Spring MVC. All three REST controllers (`OwnerResource`, `PetResource`, and `VisitResource`) are instrumented by the `@Timed` Micrometer annotation at the class level.
193
197
194
198
The `customers-service` application has the following custom metrics enabled:
195
199
196
-
-@Timed: `petclinic.owner`
197
-
-@Timed: `petclinic.pet`
200
+
-@Timed: `petclinic.owner`
201
+
-@Timed: `petclinic.pet`
198
202
199
203
The `visits-service` application has the following custom metrics enabled:
200
204
201
-
-@Timed: `petclinic.visit`
205
+
-@Timed: `petclinic.visit`
202
206
203
207
You can see these custom metrics in the `Metrics` blade:
0 commit comments