From 15b359eeec30ed205b2b329d2c789036b2741811 Mon Sep 17 00:00:00 2001 From: amal gireesh <48020356+amalgireesh@users.noreply.github.com> Date: Mon, 24 May 2021 20:01:39 +0530 Subject: [PATCH] Update README.md --- .../README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/05-build-a-spring-boot-microservice-using-spring-cloud-features/README.md b/05-build-a-spring-boot-microservice-using-spring-cloud-features/README.md index d4156a07..3d5e3358 100644 --- a/05-build-a-spring-boot-microservice-using-spring-cloud-features/README.md +++ b/05-build-a-spring-boot-microservice-using-spring-cloud-features/README.md @@ -165,7 +165,7 @@ _Please be aware it might take a couple of minutes for the logs to show up._ 1. Streaming the console output as we just did may be helpful in understanding the immediate state of a microservice. However, sometimes it's necessary to look further into the past or to look for something specific. This is easily done with Log Analytics. In exercise 3, we enabled log aggregation in Azure Log Analytics. Such settings changes can take 1-2 minutes to apply, so by now, you should be able to query Azure Log Analytics. -2. Open the Azure Portal (https://portal.azure.com) and navigate to your Azure Spring Cloud instance. Click on "Logs". This is a shortcut to the Log Analytics workspace that was created earlier. If a tutorial appears, feel free to skip it for now. +2. Open the Azure Portal and navigate to your Azure Spring Cloud instance. Click on **Logs**. This is a shortcut to the Log Analytics workspace that was created earlier. If a tutorial appears, feel free to skip it for now. 3. This workspace allows you to run queries on the aggregated logs. The most common query is to get the latest log from a specific application: