Skip to content
This repository was archived by the owner on Jan 21, 2026. It is now read-only.

Commit 64cab7d

Browse files
authored
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
1 parent 59fabdf commit 64cab7d

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

Instructions/Labs/AZ400_M04_L09_Controlling_Deployments_using_Release_Gates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ In this task, you will create two Azure web apps representing the **Canary** and
146146
> **Note**: You will create monitor alerts here, which you will use in later part of this lab.
147147
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.
148148
1. On the Application Insights resource blade, in the **Monitoring** section, click **Alerts** and then click **Create > Alert rule**.
149-
1. On the **Select a signal** blade, in the **Search by signal name** textbox, type **Failed Requests** and select it.
149+
1. On the **Select a signal** blade, in the **Search by signal name** textbox, type **Requests** and select it.
150150
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:
151151
- Aggregation Type: Count
152152
- Operator: Greater Than

0 commit comments

Comments
 (0)