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
1. Select the **type** of metrics data for each **service** you wish to monitor, and the **retention policy** for the data. You can also disable monitoring by setting **Status** to **Off**.
There are two types of metrics you can enable for each service, both of which are enabled by default for new storage accounts:
44
-
45
-
***Aggregate**: Collects metrics such as ingress/egress, availability, latency, and success percentages. These metrics are aggregated for the blob, queue, table, and file services.
46
-
***Per API**: In addition to the aggregate metrics, collects the same set of metrics for each storage operation in the Azure Storage service API.
To set the data retention policy, move the **Retention (days)** slider or enter the number of days of data to retain, from 1 to 365. The default for new storage accounts is seven days. If you do not want to set a retention policy, enter zero. If there is no retention policy, it is up to you to delete the monitoring data.
49
44
@@ -67,23 +62,21 @@ Use the following procedure to choose which storage metrics to view in a metrics
67
62
68
63
1. Start by displaying a storage metric chart in the Azure portal. You can find charts on the **storage account blade** and in the **Metrics** blade for an individual service (blob, queue, table, file).
69
64
70
-
In this example, we work with the following chart that appears on the **storage account blade**:
65
+
In this example, uses the following chart that appears on the **storage account blade**:
71
66
72
67
73
68
74
-
1. Next, click anywhere within the chart to open the **Metric** blade. Select **Edit chart** to open the **Edit Chart** blade.
75
-
76
-
69
+
1. Click anywhere within the chart to edit the chart.
77
70
78
-
1.On the **Edit Chart** blade, select the **Time Range** of the metrics to display in the chart, and the **service** (blob, queue, table, file) whose metrics you wish to display. Here we've selected to display the past week's metrics for the blob service:
71
+
1.Next, select the **Time Range** of the metrics to display in the chart, and the **service** (blob, queue, table, file) whose metrics you wish to display. Here, the past week's metrics are selected to display for the blob service:
79
72
80
-
73
+
81
74
82
-
1. Select the individual **metrics** you'd like displayed in the chart, then click **OK**. For example, here we've chosen to display the *ContainerCount* and *ObjectCount* metrics:
75
+
1. Select the individual **metrics** you'd like displayed in the chart, then click **OK**.
83
76
84
-
77
+
85
78
86
-
Your chart settings do not affect the collection, aggregation, or storage of monitoring data in the storage account, only the viewing of metrics data.
79
+
Your chart settings do not affect the collection, aggregation, or storage of monitoring data in the storage account.
87
80
88
81
### Metrics availability in charts
89
82
@@ -93,7 +86,7 @@ The list of available metrics changes based on which service you've chosen in th
93
86
94
87
### Metrics resolution
95
88
96
-
The metrics you selected in Diagnostics determines the resolution of the metrics that are available for your account:
89
+
The metrics you selected in **Diagnostics** determines the resolution of the metrics that are available for your account:
97
90
98
91
***Aggregate** monitoring provides metrics such as ingress/egress, availability, latency, and success percentages. These metrics are aggregated from the blob, table, file, and queue services.
99
92
***Per API** provides finer resolution, with metrics available for individual storage operations, in addition to the service-level aggregates.
@@ -102,14 +95,14 @@ The metrics you selected in Diagnostics determines the resolution of the metrics
102
95
103
96
You can create alerts to notify you when thresholds have been reached for storage resource metrics.
104
97
105
-
1. To open the **Alert rules blade**, scroll down to the **MONITORING** section of the **Menu blade** and select **Alert rules**.
106
-
1. Select **Add alert** to open the **Add an alert rule** blade
107
-
1. Select a **Resource** (blob, file, queue, table) from the drop-down, and enter a **Name** and **Description** for your new alert rule.
108
-
1. Select the **Metric** for which you'd like to add an alert, an alert **Condition**, and a **Threshold**. The threshold unit type changes depending on the metric you've chosen. For example, "count" is the unit type for *ContainerCount*, while the unit for the *PercentNetworkError* metric is a percentage.
109
-
1. Select the **Period**. Metrics that reach or exceed the Threshold within the period trigger an alert.
110
-
1. (Optional) Configure **Email** and **Webhook** notifications. For more information on webhooks, see [Configure a webhook on an Azure metric alert](../../monitoring-and-diagnostics/insights-webhooks-alerts.md). If you do not configure email or webhook notifications, alerts will appear only in the Azure portal.
98
+
1. To open the **Alert rules blade**, scroll down to the **MONITORING** section of the **Menu blade** and select **Alerts (classic)**.
99
+
2. Select **Add metric alert (classic)** to open the **Add an alert rule** blade
100
+
3. Enter a **Name** and **Description** for your new alert rule.
101
+
4. Select the **Metric** for which you'd like to add an alert, an alert **Condition**, and a **Threshold**. The threshold unit type changes depending on the metric you've chosen. For example, "count" is the unit type for *ContainerCount*, while the unit for the *PercentNetworkError* metric is a percentage.
102
+
5. Select the **Period**. Metrics that reach or exceed the Threshold within the period trigger an alert.
103
+
6. (Optional) Configure **Email** and **Webhook** notifications. For more information on webhooks, see [Configure a webhook on an Azure metric alert](../../monitoring-and-diagnostics/insights-webhooks-alerts.md). If you do not configure email or webhook notifications, alerts will appear only in the Azure portal.
111
104
112
-
105
+
113
106
114
107
## Add metrics charts to the portal dashboard
115
108
@@ -122,7 +115,7 @@ You can add Azure Storage metrics charts for any of your storage accounts to you
122
115
1. Select **Categories** > **Monitoring**.
123
116
1. Drag-and-drop the chart tile onto your dashboard for the metric you'd like displayed. Repeat for all metrics you'd like displayed on the dashboard. In the following image, the "Blobs - Total requests" chart is highlighted as an example, but all the charts are available for placement on your dashboard.
124
117
125
-
118
+
126
119
1. Select **Done customizing** near the top of the dashboard when you're done adding charts.
127
120
128
121
Once you've added charts to your dashboard, you can further customize them as described in [Customize metrics charts](#how-to-customize-metrics-charts).
@@ -138,14 +131,14 @@ You can instruct Azure Storage to save diagnostics logs for read, write, and del
138
131
1. In the [Azure portal](https://portal.azure.com), select **Storage accounts**, then the name of the storage account to open the storage account blade.
139
132
1. Select **Diagnostics** in the **MONITORING** section of the menu blade.
140
133
141
-
134
+
142
135
143
136
1. Ensure **Status** is set to **On**, and select the **services** for which you'd like to enable logging.
144
137
145
-
138
+
146
139
1. Click **Save**.
147
140
148
-
The diagnostics logs are saved in a blob container named $logs in your storage account. You can view the log data using a storage explorer like the [Microsoft Storage Explorer](http://storageexplorer.com), or programmatically using the storage client library or PowerShell.
141
+
The diagnostics logs are saved in a blob container named *$logs* in your storage account. You can view the log data using a storage explorer like the [Microsoft Storage Explorer](http://storageexplorer.com), or programmatically using the storage client library or PowerShell.
149
142
150
143
For information about accessing the $logs container, see [Enabling Storage Logging and Accessing Log Data](/rest/api/storageservices/enabling-storage-logging-and-accessing-log-data).
0 commit comments