Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 89cec08

Browse files
author
dksimpson
committedSep 2, 2017
story 403, update 4 screen shot to match current screens, Acrolynx edits
1 parent 95db2d8 commit 89cec08

File tree

5 files changed

+13
-13
lines changed

5 files changed

+13
-13
lines changed
 

‎articles/cdn/cdn-real-time-alerts.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -29,12 +29,12 @@ This document explains real-time alerts in Microsoft Azure CDN. This functionali
2929
* Connections
3030

3131
## Creating a real-time alert
32-
1. In the [Azure Portal](https://portal.azure.com), browse to your CDN profile.
32+
1. In the [Azure portal](https://portal.azure.com), browse to your CDN profile.
3333

34-
![CDN profile blade](./media/cdn-real-time-alerts/cdn-profile-blade.png)
35-
2. From the CDN profile blade, click the **Manage** button.
34+
![CDN profile](./media/cdn-real-time-alerts/cdn-profile-blade.png)
35+
1. From the CDN profile blade, click the **Manage** button.
3636

37-
![CDN profile blade manage button](./media/cdn-real-time-alerts/cdn-manage-btn.png)
37+
![CDN profile manage button](./media/cdn-real-time-alerts/cdn-manage-btn.png)
3838

3939
The CDN management portal opens.
4040
3. Hover over the **Analytics** tab, then hover over the **Real-Time Stats** flyout. Click on **Real-Time Alerts**.
@@ -56,26 +56,26 @@ This document explains real-time alerts in Microsoft Azure CDN. This functionali
5656
![Media Type with HTTP Large Object selected](./media/cdn-real-time-alerts/cdn-http-large.png)
5757

5858
> [!IMPORTANT]
59-
> You must select **HTTP Large Object** as the **Media Type**. The other choices are not used by **Azure CDN from Verizon**. Failure to select **HTTP Large Object** will cause your alert to never be triggered.
59+
> You must select **HTTP Large Object** as the **Media Type**. The other choices are not used by **Azure CDN from Verizon**. Failure to select **HTTP Large Object** causes your alert to never be triggered.
6060
>
6161
>
6262
8. Create an **Expression** to monitor by selecting a **Metric**, **Operator**, and **Trigger value**.
6363

6464
* For **Metric**, select the type of condition you want monitored. **Bandwidth Mbps** is the amount of bandwidth usage in megabits per second. **Total Connections** is the number of concurrent HTTP connections to our edge servers. For definitions of the various cache statuses and status codes, see [Azure CDN Cache Status Codes](https://msdn.microsoft.com/library/mt759237.aspx) and [Azure CDN HTTP Status Codes](https://msdn.microsoft.com/library/mt759238.aspx)
6565
* **Operator** is the mathematical operator that establishes the relationship between the metric and the trigger value.
66-
* **Trigger Value** is the threshold value that must be met before a notification will be sent out.
66+
* **Trigger Value** is the threshold value that must be met before a notification is sent.
6767

68-
In the below example, the expression I have created indicates that I would like to be notified when the number of 404 status codes is greater than 25.
68+
In the following example, the created expression indicates that a notification is sent when the number of 404 status codes is greater than 25.
6969

7070
![Real-time alert sample expression](./media/cdn-real-time-alerts/cdn-expression.png)
7171
9. For **Interval**, enter how frequently you would like the expression evaluated.
7272
10. In the **Notify on** dropdown, select when you would like to be notified when the expression is true.
7373

74-
* **Condition Start** indicates that a notification will be sent when the specified condition is first detected.
75-
* **Condition End** indicates that a notification will be sent when the specified condition is no longer detected. This notification can only be triggered after our network monitoring system detected that the specified condition occurred.
76-
* **Continuous** indicates that a notification will be sent each time that the network monitoring system detects the specified condition. Keep in mind that the network monitoring system will only check once per interval for the specified condition.
77-
* **Condition Start and End** indicates that a notification will be sent the first time that the specified condition is detected and once again when the condition is no longer detected.
78-
11. If you want to receive notifications by email, check the **Notify by Email** checkbox.
74+
* **Condition Start** indicates that a notification is sent when the specified condition is first detected.
75+
* **Condition End** indicates that a notification is sent when the specified condition is no longer detected. This notification can only be triggered after our network monitoring system detected that the specified condition occurred.
76+
* **Continuous** indicates that a notification is sent each time that the network monitoring system detects the specified condition. Keep in mind that the network monitoring system checks only once per interval for the specified condition.
77+
* **Condition Start and End** indicates that a notification is sent the first time that the specified condition is detected and once again when the condition is no longer detected.
78+
1. If you want to receive notifications by email, check the **Notify by Email** checkbox.
7979

8080
![Notify by Email form](./media/cdn-real-time-alerts/cdn-notify-email.png)
8181

@@ -89,7 +89,7 @@ This document explains real-time alerts in Microsoft Azure CDN. This functionali
8989

9090
![Notify by HTTP Post form](./media/cdn-real-time-alerts/cdn-notify-http.png)
9191

92-
In the **Url** field, enter the URL you where you want the HTTP message posted. In the **Headers** textbox, enter the HTTP headers to be sent in the request. For **Body** you may customize the message using the **Available keywords** list to dynamically insert alert data when the message is sent. **Headers** and **Body** default to an XML payload similar to the below example.
92+
In the **Url** field, enter the URL you where you want the HTTP message posted. In the **Headers** textbox, enter the HTTP headers to be sent in the request. For **Body**, you may customize the message by using the **Available keywords** list to dynamically insert alert data when the message is sent. **Headers** and **Body** default to an XML payload similar to the following example:
9393

9494
```
9595
<string xmlns="http://schemas.microsoft.com/2003/10/Serialization/">
Loading
Loading
Loading
Loading

0 commit comments

Comments
 (0)
Please sign in to comment.