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
Copy file name to clipboardExpand all lines: learn-pr/azure/monitor-diagnose-and-troubleshoot-azure-storage/includes/2-storage-troubleshooting-tools.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Storage insights provide a unified view of your Azure Storage services performan
39
39
40
40
You can process metric values by creating batch jobs in Azure CLI, PowerShell scripts, or by writing code that uses a storage client library. You can also archive transaction metrics to a storage account, and then view or process them by using these same tools.
41
41
42
-
If you choose to archive transaction metrics to a storage account, metric data is collected and stored inside a single blob as a line-delimited JSON payload. You can view those blobs by opening the relevant log container in the Azure portal or by using [Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer/). You can also download those blobs to your local computer and process them by using tools and SDKs.
42
+
If you choose to archive transaction metrics to a storage account, metric data is collected and stored inside a single blob as a line-delimited JSON payload. You can view those blobs by opening the relevant log container in the Azure portal or by using [Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer/). You can also download those blobs to your local computer and process them by using tools and Software Development Kits (SDKs).
In this exercise, we'll use Azure portal and PowerShell to configure storage metrics for our storage account. We'll upload some files to Blob Storage, and then look at metrics in Metrics Explorer.
1
+
In this exercise, we use the Azure portal to create a storage account and configure storage metrics. Next, we upload some files to Blob Storage, and then look at our storage metrics in Metrics Explorer.
2
2
3
3
## Create a storage account
4
4
5
5
1. Select [this link](https://portal.azure.com/learn.docs.microsoft.com?azure-portal=true) to sign in to the Azure portal by using the same account with which you activated the sandbox.
6
6
7
-
2. In the Azure portal, select **Create a resource**.
7
+
1. In the Azure portal, select **Create a resource**.
8
8
9
-
3. In the **Search services and Marketplace** box, search for and select **Storage account**.
9
+
1. In the **Search services and Marketplace** box, search for and select **Storage account**.
10
10
11
11
The **Storage account** panel appears.
12
12
13
-
4. Select **Create**.
13
+
1. Select **Create**.
14
14
15
-
The **Create storage account** panel appears.
15
+
The **Create a storage account** panel appears.
16
16
17
-
5. On the **Basics** tab, fill in the following values for each setting.
17
+
1. On the **Basics** tab, fill in the following values for each setting.
18
18
19
19
| Setting | Value |
20
20
|---|---|
@@ -27,21 +27,21 @@ In this exercise, we'll use Azure portal and PowerShell to configure storage met
27
27
| Performance |**Standard**|
28
28
| Redundancy |**Geo-redundant storage (GRS)**|
29
29
30
-
6. Select the **Advanced** tab. In the **Blob storage** section, make sure that **access tier** is set to **Hot**.
30
+
1. Select the **Advanced** tab. In the **Blob storage** section, make sure that **access tier** is set to **Hot**.
31
31
32
-
7. Select **Review**. After validation passes, select **Create**.
32
+
1. Select **Review + Create**. After validation passes, select **Create**.
33
33
34
-
8. On the **Your deployment is complete** panel, select **Go to resource**.
34
+
1. When you see the message **Your deployment is complete**, select **Go to resource**.
35
35
36
36
## Add a blob container
37
37
38
38
Before you can add blobs to a storage account, you need to create a blob container.
39
39
40
-
1.Under**Data storage**, select **Containers**.
40
+
1.In the menu pane, under**Data storage**, select **Containers**.
41
41
42
-
2. In the **Containers**panel, select **+ Container**.
42
+
1. In the **Containers**tool bar, select **+ Add container**.
43
43
44
-
3. In the **Name** field, enter **monitor-blobs-container**, then select **Create**.
44
+
1. In the **Name** field, enter **monitor-blobs-container**, then select **Create**.
45
45
46
46
## Upload files to the blob container
47
47
@@ -63,19 +63,19 @@ To upload a single file to the blob container:
63
63
64
64
## Visualize metrics in the Azure portal
65
65
66
-
Transaction metrics are emitted on every request to a storage account, so you should see changes in these values relatively quickly. To create a transaction metrics chart, complete the following steps:
66
+
Transaction metrics are emitted on every request to a storage account, so you should see changes in these values fairly quickly. To create a transaction metrics chart, complete the following steps:
67
67
68
68
1. In the Azure portal, navigate to the page for your storage account.
69
69
70
-
2. In the menu pane, under **Monitoring**, select **Metrics**.
70
+
1. In the menu pane, under **Monitoring**, select **Metrics**.
71
71
72
-
3. In the top right, select **Last hour** for the time range.
72
+
1. In the top right, select **Last hour** for the time range.
73
73
74
-
4. Under **Time granularity**, select **Automatic**, then select **Apply**.
74
+
1. Under **Time granularity**, select **Automatic**, then select **Apply**.
75
75
76
-
5. On the bar that appears beneath the chart title, select **Line chart**, and then **Bar chart**.
76
+
1. On the bar that appears beneath the chart title, select **Line chart**, and then **Bar chart**.
77
77
78
-
6. Change the **metric namespace** to **Blob** and select **Ingress** for the **metric**.
78
+
1. Change the **metric namespace** to **Blob** and select **Ingress** for the **Metric**.
79
79
80
80
The following image shows a bar for every file upload operation in the last hour.
81
81
@@ -84,11 +84,11 @@ Transaction metrics are emitted on every request to a storage account, so you sh
84
84
85
85
## Split a metric
86
86
87
-
Splitting a metric lets you view additional dimensions in the data. For each file that you uploaded, the Azure portal made several API calls. Each request resulted in bytes transferred. You can split the ingress metric by the API dimension to see the breakdown of bytes transferred by API call. To split a metric, complete the following steps:
87
+
Splitting a metric lets you view other dimensions in the data. For each file that you uploaded, the Azure portal made several API calls. Each request resulted in bytes transferred. You can split the ingress metric by the API dimension to see the breakdown of bytes transferred by API call. To split a metric, complete the following steps:
88
88
89
-
1. Select **Apply splitting**
89
+
1. Select **Apply splitting**.
90
90
91
-
2. In the **Splitting**oval, from the drop-down list, select **API name**.
91
+
1. In the **Splitting**box, from the**Values** drop-down list, select **API name**.
92
92
93
93
View the output in the chart window. The following image shows bytes transferred by API call.
94
94
@@ -101,13 +101,13 @@ Filtering lets you look at the metrics with greater granularity. You can use a f
101
101
102
102
1. Select **Add filter**.
103
103
104
-
2. Under **Property**, select **API name**.
104
+
1. Under **Property**, select **API name**.
105
105
106
-
3. Under **Values**, select **PutBlob**.
106
+
1. Under **Values**, select **PutBlob**.
107
107
108
-
The chart shows bars that represent the REST call to the **Put Blob** API.
108
+
The chart shows bars that represent the REST call to the **PutBlob** API.
109
109
110
110
> [!div class="mx-imgBorder"]
111
111
> 
112
112
113
-
4. Select the **X** to the right of the filter oval to remove the filter.
113
+
1. Select the **X** to the right of the filter box to remove the filter.
Copy file name to clipboardExpand all lines: learn-pr/azure/monitor-diagnose-and-troubleshoot-azure-storage/includes/5-storage-logging.md
+19-22Lines changed: 19 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,50 +1,47 @@
1
-
Azure Storage resource logs capture each operation performed in your storage account, as well as the outcome of these operations. These logs provide details about each request made rather than providing the minute-by-minute summary of operations that the metrics show. Using the logging information, you can examine the nature of requests made to a storage account and determine whether these requests are successful.
1
+
Azure Storage resource logs capture each operation performed in your storage account and the outcome of these operations. These logs provide details about each request made rather than providing the minute-by-minute summary of operations that the metrics show. Using the logging information, you can examine the nature of requests made to a storage account and determine whether these requests are successful.
2
2
3
-
In this unit, you'll learn about Azure Storage resource logs in Azure Monitor. You'll see the different types of information captured in logs, and how you might use this information to detect problems that might occur when an application uses Azure Storage.
3
+
In this unit, you learn about Azure Storage resource logs in Azure Monitor. You see the different types of information captured in logs, and learn how you can use this information to detect problems that might occur when an application uses Azure Storage.
4
4
5
5
## Resource Logs in Azure Monitor
6
6
7
-
Sometimes you want to see more detail about storage transactions than performance-related metrics. Metrics are useful for tracking overall trends in performance or demand, but monitoring the transaction metrics can't reveal the requested URLs. Also, none of the available storage metrics can give error messages that relate to a specific request.
7
+
Sometimes you want to see more detail about storage transactions than performance-related metrics. Metrics are useful for tracking overall trends in performance or demand, but monitoring the transaction metrics can't reveal the requested URLs. Also, none of the available storage metrics can report error messages that relate to a specific request.
8
8
9
9
Resource logs in Azure Monitor capture this kind of detailed information, and they're useful for examining the detail behind specific requests. For example, you can use these logs if you want to know how many requests for a specific resource are authenticated or anonymous, or successful, or failed.
10
10
11
11
To collect resource logs, you must create a diagnostic setting. Resource logs list successful and failed requests for a storage account. Requests are recorded as read, write, or delete operations against the specific storage service: Azure Blob Storage, Table Storage, or Queue Storage. By using a diagnostic setting, you can route logs to Log Analytics, a storage account, or stream them to an event hub or to a partner solution.
12
12
13
-
You can use resource logs to review different types and frequency of requests, or to troubleshoot failed requests. Logs are generated only when transactions occur, and only for the specific service endpoint. Therefore, if you're using storage in the Blob Storage and Queue Storage endpoints, but only the Blob Storage endpoint has requests or transactions, then the system will create logs only for Blob Storage.
13
+
You can use resource logs to review different types and frequency of requests, or to troubleshoot failed requests. Logs are generated only when transactions occur, and only for the specific service endpoint. Therefore, if you're using storage in the Blob Storage and Queue Storage endpoints, but only the Blob Storage endpoint has requests or transactions, then the system creates logs only for Blob Storage.
14
14
15
15
When you enable logging, these types of requests are logged:
16
16
17
-
* Authenticated requests
18
-
* Anonymous requests
19
-
* Successful requests
20
-
* Failed requests, such as timeouts, throttling, network errors, and authorization errors
21
-
* Server errors
22
-
* Requests that use a shared access signature, both failed and successful
23
-
* Timeout errors for client and server
24
-
* Requests to analytics data
25
-
*GET requests with error code 304 ("Not Modified")
17
+
- Authenticated requests.
18
+
- Anonymous requests.
19
+
- Successful requests.
20
+
- Failed requests. Such as, timeouts, throttling, network errors, and authorization errors.
21
+
- Server errors.
22
+
- Requests that use a shared access signature, both failed and successful.
23
+
- Timeout errors for client and server.
24
+
- Requests to analytics data.
25
+
- Failed GET requests with error code 304 ("Not Modified").
26
26
27
27
## Storage of resource logs in Azure Monitor
28
28
29
29
Resource logs are automatically generated for your storage account, but those logs aren't available to view unless you send them to a destination. You can specify where to send them by using a diagnostic setting.
30
30
31
-
When you create a diagnostic setting, you choose the type of storage for which you're interested in routing logs (for example: Blob Storage or File Storage). Then, you'll choose which types of operations you want to appear in logs (for example: read, write, or delete operations). Finally, you'll choose where you would like logs to be sent. You can send log to any of these locations:
31
+
When you create a diagnostic setting, you choose the type of storage for which you're interested in routing logs. For example, Blob Storage or File Storage. Then, you choose which types of operations you want to appear in the logs. For example, read, write, or delete operations. Finally, you choose where you would like logs to be sent. You can send logs to any of these locations:
32
32
33
-
* Log Analytics
34
-
35
-
* Storage account
36
-
37
-
* Event hub
38
-
39
-
* A partner solution
33
+
- Log Analytics
34
+
- Storage account
35
+
- Event hub
36
+
- A partner solution
40
37
41
38
You can access logs sent to a Log Analytics workspace by using Azure Monitor log queries.
42
39
43
40
If you route logs to a storage account, those logs appear as blobs stored to a container. Data is collected and stored inside a single blob as a line-delimited JSON payload. The name of the blob follows this naming convention:
Logs sent to an event hub aren't stored as a file, but you can verify that the event hub received the log information by opening your event hub in the Azure portal and examining the incoming messages count.
44
+
Logs sent to an event hub aren't stored as a file, but you can verify that the event hub received the log information. Just open your event hub in the Azure portal and examining the count of incoming messages.
48
45
49
46
You can also send platform metrics and logs to certain Azure Monitor partners. You must first install a partner integration into your subscription. Configuration options vary by partner.
0 commit comments