From 64cab7d9d278be39809f6e1b4874ee68e1496952 Mon Sep 17 00:00:00 2001
From: sattract <114693937+sattract@users.noreply.github.com>
Date: Wed, 1 Feb 2023 03:47:46 +0530
Subject: [PATCH] Changing signal name

Changing signal name from **Failed Requests**  to **Requests** because failed requests doesn't exist.

No affect to the further process of lab
---
 ...AZ400_M04_L09_Controlling_Deployments_using_Release_Gates.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Instructions/Labs/AZ400_M04_L09_Controlling_Deployments_using_Release_Gates.md b/Instructions/Labs/AZ400_M04_L09_Controlling_Deployments_using_Release_Gates.md
index 7f6db0c97..e0079d5dd 100644
--- a/Instructions/Labs/AZ400_M04_L09_Controlling_Deployments_using_Release_Gates.md
+++ b/Instructions/Labs/AZ400_M04_L09_Controlling_Deployments_using_Release_Gates.md
@@ -146,7 +146,7 @@ In this task, you will create two Azure web apps representing the **Canary** and
     > **Note**: You will create monitor alerts here, which you will use in later part of this lab.
 1. From the same **Settings** / **Application Insights** menu option, select **View Application Insight Data**. This redirects you to the Application Insights blade in the Azure Portal.
 1.  On the Application Insights resource blade, in the **Monitoring** section, click **Alerts** and then click **Create > Alert rule**.
-1.  On the **Select a signal** blade, in the **Search by signal name** textbox, type **Failed Requests** and select it. 
+1.  On the **Select a signal** blade, in the **Search by signal name** textbox, type **Requests** and select it. 
 1.  On the **Create an Alert Rule** blade, in the **Condition** section, leave the **Threshold** set to **Static**, validate the other default settings as follows:
 - Aggregation Type: Count
 - Operator: Greater Than