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
@@ -35,10 +41,10 @@ The following table lists some example scenarios to monitor and the proper metri
35
41
36
42
| Scenario | Metric to use for alert |
37
43
|-|-|
38
-
| File share is throttled. | Metric: Transactions<br>Dimension name: Response type <br>Dimension name: FileShare (premium file share only) |
39
-
| File share size is 80% of capacity. | Metric: File Capacity<br>Dimension name: FileShare (premium file share only) |
40
-
| File share egress has exceeded 500 GiB in one day. | Metric: Egress<br>Dimension name: FileShare (premium file share only) |
41
-
| File share availability is less than 99.9%. | Metric: Availability<br>Dimension name: FileShare (premium file share only) |
44
+
| File share is throttled. | Metric: Transactions<br>Dimension name: Response type <br>Dimension name: FileShare (provisioned file shares only) |
45
+
| File share size is 80% of capacity. | Metric: File Capacity<br>Dimension name: FileShare (provisioned file shares only) |
46
+
| File share egress has exceeded 500 GiB in one day. | Metric: Egress<br>Dimension name: FileShare (provisioned file shares only) |
47
+
| File share availability is less than 99.9%. | Metric: Availability<br>Dimension name: FileShare (provisioned file shares only) |
42
48
43
49
## How to create an alert if a file share is throttled
44
50
@@ -56,13 +62,13 @@ To create an alert that will notify you if a file share is being throttled, foll
56
62
57
63
6. In the **Dimension values** drop-down list, select the appropriate response types for your file share.
58
64
59
-
For standard file shares, select the following response types:
65
+
For pay-as-you-go file shares, select the following response types:
60
66
61
67
-`SuccessWithShareIopsThrottling`
62
68
-`SuccessWithThrottling`
63
69
-`ClientShareIopsThrottlingError`
64
70
65
-
For premium file shares, select the following response types:
71
+
For provisioned file shares, select the following response types:
66
72
67
73
-`SuccessWithShareEgressThrottling`
68
74
-`SuccessWithShareIngressThrottling`
@@ -74,10 +80,10 @@ To create an alert that will notify you if a file share is being throttled, foll
74
80
> [!NOTE]
75
81
> If the response types aren't listed in the **Dimension values** drop-down, this means the resource hasn't been throttled. To add the dimension values, next to the **Dimension values** drop-down list, select **Add custom value**, enter the response type (for example, **SuccessWithThrottling**), select **OK**, and then repeat these steps to add all applicable response types for your file share.
76
82
77
-
5. For **premium file shares**, select the **Dimension name** drop-down and select **File Share**. For **standard file shares**, skip to step 7.
83
+
5. For **provisioned file shares**, select the **Dimension name** drop-down and select **File Share**. For **pay-as-you-go file shares**, skip to step 8.
78
84
79
85
> [!NOTE]
80
-
> If the file share is a standard file share, the **File Share** dimension won't list the file share(s) because per-share metrics aren't available for standard file shares. Throttling alerts for standard file shares will be triggered if any file share within the storage account is throttled, and the alert won't identify which file share was throttled. Because per-share metrics aren't available for standard file shares, the recommendation is to have one file share per storage account.
86
+
> If the file share is a pay-as-you-go file share, the **File Share** dimension won't list the file share(s) because pershare metrics aren't available for pay-as-you-go file shares. Throttling alerts for pay-as-you-go file shares will be triggered if any file share within the storage account is throttled, and the alert won't identify which file share was throttled. Because pershare metrics aren't available for pay-as-you-go file shares, we recommend using the provisioned v2 model instead of the pay-as-you-go model.
81
87
82
88
6. Select the **Dimension values** drop-down and select the file share(s) that you want to alert on.
83
89
@@ -102,10 +108,10 @@ To create an alert that will notify you if a file share is being throttled, foll
102
108
103
109
4. In the **Condition** tab of the **Create an alert rule** dialog box, select the **File Capacity** metric.
104
110
105
-
5. For **premium file shares**, select the **Dimension name** drop-down list, and then select **File Share**. For **standard file shares**, skip to step 5.
111
+
5. For **provisioned file shares**, select the **Dimension name** drop-down list, and then select **File Share**. For **pay-as-you-go file shares**, skip to step 6.
106
112
107
113
> [!NOTE]
108
-
> If the file share is a standard file share, the **File Share** dimension won't list the file share(s) because per-share metrics aren't available for standard file shares. Alerts for standard file shares are based on all file shares in the storage account. Because per-share metrics aren't available for standard file shares, the recommendation is to have one file share per storage account.
114
+
> If the file share is a pay-as-you-go file share, the **File Share** dimension won't list the file share(s) because pershare metrics aren't available for pay-as-you-go file shares. Throttling alerts for pay-as-you-go file shares will be triggered if any file share within the storage account is throttled, and the alert won't identify which file share was throttled. Because pershare metrics aren't available for pay-as-you-go file shares, we recommend using the provisioned v2 model instead of the pay-as-you-go model.
109
115
110
116
6. Select the **Dimension values** drop-down and select the file share(s) that you want to alert on.
111
117
@@ -129,22 +135,22 @@ To create an alert that will notify you if a file share is being throttled, foll
129
135
130
136
4. In the **Condition** tab of the **Create an alert rule** dialog box, select the **Egress** metric.
131
137
132
-
5. For **premium file shares**, select the **Dimension name** drop-down list and select **File Share**. For **standard file shares**, skip to step 5.
138
+
5. For **provisioned file shares**, select the **Dimension name** drop-down list and select **File Share**. For **pay-as-you-go file shares**, skip to step 6.
133
139
134
140
> [!NOTE]
135
-
> If the file share is a standard file share, the **File Share** dimension won't list the file share(s) because per-share metrics aren't available for standard file shares. Alerts for standard file shares are based on all file shares in the storage account. Because per-share metrics aren't available for standard file shares, the recommendation is to have one file share per storage account.
141
+
> If the file share is a pay-as-you-go file share, the **File Share** dimension won't list the file share(s) because pershare metrics aren't available for pay-as-you-go file shares. Throttling alerts for pay-as-you-go file shares will be triggered if any file share within the storage account is throttled, and the alert won't identify which file share was throttled. Because pershare metrics aren't available for pay-as-you-go file shares, we recommend using the provisioned v2 model instead of the pay-as-you-go model.
136
142
137
-
4. Select the **Dimension values** drop-down and select the file share(s) that you want to alert on.
143
+
6. Select the **Dimension values** drop-down and select the file share(s) that you want to alert on.
138
144
139
-
5. Enter **536870912000** bytes for Threshold value.
145
+
7. Enter **536870912000** bytes for Threshold value.
140
146
141
-
6. From the **Check every** drop-down list, select the frequency of evaluation.
147
+
8. From the **Check every** drop-down list, select the frequency of evaluation.
142
148
143
-
7. Select the **Actions** tab to add an action group (email, SMS, etc.) to the alert. You can select an existing action group or create a new action group.
149
+
9. Select the **Actions** tab to add an action group (email, SMS, etc.) to the alert. You can select an existing action group or create a new action group.
144
150
145
-
8. Select the **Details** tab to fill in the details of the alert such as the alert name, description, and severity.
151
+
10. Select the **Details** tab to fill in the details of the alert such as the alert name, description, and severity.
146
152
147
-
9. Select **Review + create** to create the alert.
153
+
11. Select **Review + create** to create the alert.
148
154
149
155
## How to create an alert for high server latency
150
156
@@ -197,7 +203,7 @@ To create an alert for high server latency (average), follow these steps.
197
203
- Select the **Dimension values** drop-down and select the file share(s) that you want to alert on.
198
204
199
205
> [!NOTE]
200
-
> If the file share is a standard file share, the **File Share** dimension won't list the file share(s) because per-share metrics aren't available for standard file shares. Availability alerts for standard file shares will be at the storage account level.
206
+
> If the file share is a pay-as-you-go file share, the **File Share** dimension won't list the file share(s) because pershare metrics aren't available for pay-as-you-go file shares. Availability alerts for pay-as-you-go file shares will be at the storage account level. We recommend using the provisioned v2 model instead of the pay-as-you-go model.
201
207
202
208
7. In the **When to evaluate** section, select the following:
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments