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/1-introduction.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
Azure Storage is a fundamental part of many Azure applications. You can use it to store the critical data your applications require. It's vital to ensure any problems or performance issues with your storage accounts are identified and fixed quickly.
2
2
3
-
Consider an automobile parts distributor who has released the latest updates of their customer portal. The distributor recently received error reports from users when viewing the files they've uploaded. You know the data was moved recently to Azure Storage. As part of the team working on the release, you're unsure of the cause of these issues. You'll troubleshoot and correct the problem to restore functionality for your customers.
3
+
Consider an automobile parts distributor who released the latest updates of their customer portal. The distributor recently received error reports from users when they're viewing the files they uploaded. You know that this data was recently moved to Azure Storage. As part of the team working on the release, you're unsure of the cause of these issues. You want to troubleshoot and correct the problem to restore functionality for your customers.
4
4
5
-
In this module, you'll learn about monitoring, troubleshooting, and diagnosing problems with your Azure Storage. You'll also learn about some of the tools that are available and how to use them.
5
+
In this module, you learn about monitoring, troubleshooting, and diagnosing problems with your Azure Storage. You also learn about some of the tools that are available for troubleshooting Azure Storage issues and how to use them.
Copy file name to clipboardExpand all lines: learn-pr/azure/monitor-diagnose-and-troubleshoot-azure-storage/includes/2-storage-troubleshooting-tools.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,22 @@
1
1
Diagnosing and troubleshooting issues for an application hosted in a cloud environment can be more complicated than in traditional environments. To support these types of applications successfully, you should monitor them and understand how to diagnose and troubleshoot any aspects of those applications and their dependent technologies. You can use a combination of tools and logging to identify issues.
2
2
3
-
In this unit, you'll learn about some of the different tools you can use to analyze issues with Azure Storage.
3
+
In this unit, you learn about some of the different tools you can use to analyze issues with Azure Storage.
4
4
5
5
## Tools available for monitoring metrics
6
6
7
-
Azure Monitor collects numeric data (*metrics*) from your storage account and makes that data available in a time-series database. Metrics are numerical values that describe some aspect of a storage account at a particular time. The Azure portal gives you a graphical way to view these metrics in near real time. There can be a delay of a few minutes between the time a metric is recorded to the time that they appear on the Azure portal. In the Azure portal, you can:
7
+
Azure Monitor collects numeric data (*metrics*) from your storage account and makes that data available in a time-series database. Metrics are numerical values that describe some aspect of a storage account at a particular time. The Azure portal gives you a graphical way to view these metrics in near real time. There can be a delay of a few minutes between the time a metric is recorded and the time that it appears on the Azure portal. In the Azure portal, you can:
8
8
9
-
- Configure metrics (*and logging*)
9
+
- Configure metrics (*and logging*).
10
10
11
-
- View graphs and charts and select which metrics to visualize
11
+
- View graphs and charts and select which metrics to visualize.
12
12
13
-
- Assess how your applications are doing over some time
13
+
- Assess how your applications are doing over a specified time.
14
14
15
-
- Configure alerts to notify you of any behavior that is out of the ordinary
15
+
- Configure alerts to notify you of any behavior that is out of the ordinary.
16
16
17
17
### Overview page Monitoring tab
18
18
19
-
You can obtain snapshot view of common metrics by opening the **Monitoring** tab on the storage account's **Overview** page. The following image shows an example that includes the ingress and egress for a storage account:
19
+
You can obtain a snapshot view of common metrics by opening the **Monitoring** tab on the storage account's **Overview** page. The following image shows an example that includes the ingress and egress for a storage account:
20
20
21
21
> [!div class="mx-imgBorder"]
22
22
> 
@@ -39,13 +39,13 @@ 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 will be 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 [Storage Explorer](https://azure.microsoft.com/features/storage-explorer/). You can also download those blobs 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 SDKs.
43
43
44
44
## Tools available for reviewing log data
45
45
46
46
There are two types of logs in Azure Monitor: activity logs and resource logs.
47
47
48
-
Activity logs provide insight into the operations on each Azure resource in the subscription from the outside (*the management plane*) in addition to updates on Service Health events. This module doesn't explore activity logs.
48
+
Activity logs provide insight into the operations on each Azure resource in the subscription from the outside (*the management plane*). They also provide updates on Service Health events. This module doesn't explore activity logs.
49
49
50
50
Resource logs (commonly referred to as *diagnostic logs*) capture detailed information about operations on storage account resources such as blobs or files. To view these logs, you need to route them to a location in Azure. Then, you can use tools to view and analyze them.
51
51
@@ -58,6 +58,6 @@ If you route logs to Log Analytics, then you can review log data by running quer
58
58
59
59
### Tools that process archived logs
60
60
61
-
If you choose to archive your logs to a storage account, you can view those logs by opening the relevant log container in the Azure portal or by using [Storage Explorer](https://azure.microsoft.com/products/storage/storage-explorer/). To download logs to your local computer, you can use either of those tools as well as the [AzCopy](/azure/storage/common/storage-use-azcopy-v10) utility.
61
+
If you choose to archive your logs to a storage account, you can view those logs by opening the relevant log container in the Azure portal or by using [Azure Storage Explorer](https://azure.microsoft.com/products/storage/storage-explorer/). To download logs to your local computer, you can use either of those tools and the [AzCopy](/azure/storage/common/storage-use-azcopy-v10) utility.
62
62
63
63
Viewing individual logs can be time consuming so might consider processing logs by using some sort of automation. You can process logs by creating batch jobs in Azure CLI, PowerShell scripts, or by writing code that uses a storage client library.
Copy file name to clipboardExpand all lines: learn-pr/azure/monitor-diagnose-and-troubleshoot-azure-storage/includes/3-storage-metrics.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
It's important to understand storage metrics so you know which metrics to examine and what these metrics indicate about the state of a storage account. Using Azure Storage metrics, you can analyze your applications' usage trends and diagnose possible issues with your storage account.
2
2
3
-
In this unit, you'll learn about metrics in Azure Monitor, what information it reports on, and how you can use the metrics it provides to identify problems with how your applications are using Azure Storage.
3
+
In this unit, you learn about metrics in Azure Monitor. In particular, the information it reports on, and how you can use the metrics it provides to identify problems with how your applications are using Azure Storage.
4
4
5
5
## Understand metrics
6
6
@@ -12,7 +12,7 @@ Capacity metrics describe data storage (for example: bytes stored, bytes still a
12
12
13
13
### Transaction metrics
14
14
15
-
Transaction metrics describe account activity (for example: number of transactions or number of bytes read). Transaction metrics are emitted on every request to a storage account from Azure Storage to Azure Monitor. In the case of no activity on your storage account, there will be no data on transaction metrics in the period. The time grain defines the time interval that metric values are presented. The supported time grains for all transaction metrics are PT1H and PT1M.
15
+
Transaction metrics describe account activity (for example: number of transactions or number of bytes read). Transaction metrics are emitted on every request to a storage account from Azure Storage to Azure Monitor. If there's no activity on your storage account during a certain time range, then there are no transaction metrics reported during that time range. The time grain defines the time interval that metric values are presented for. The supported time grains for all transaction metrics are PT1H and PT1M.
16
16
17
17
## The anatomy of a metric value
18
18
@@ -22,13 +22,13 @@ You can get metric values by providing a time range, time interval, metric names
22
22
|---|---|
23
23
| Time range | The period of time that you want to capture (for example: yesterday or the last month). |
24
24
| Time interval | The granularity of time reflected by a metric value. (for example: a value that reflects one hour or one day). |
25
-
| Metric namespace | The namespace of the metric. This specifies whether to get a metric at the storage account level, or at the level of a specific storage service (for example: File Storage). |
26
-
| Metric name | The metric you're interested in (for example: egress). |
27
-
| Aggregation | How you want that value calculated. In most cases, you'll choose either a sum or an average. |
25
+
| Metric namespace | The namespace of the metric. The namespace specifies whether to get a metric at the storage account level, or at the level of a specific storage service (for example: *File Storage*). |
26
+
| Metric name | The metric you're interested in (for example: *egress*). |
27
+
| Aggregation | How you want that value calculated. In most cases, you choose either a *sum* or an *average*. |
28
28
29
-
For metrics that support dimensions, you can filter the metric with the desired dimension value. Dimensions are name/value pairs that carry additional data to describe the metric value. For example, authentication type is a dimension for transactions. If you're interested in seeing only transactions that were authorized by using an account key, you can use the authentication dimension and filter on account key.
29
+
For metrics that support dimensions, you can filter the metric with the desired dimension value. Dimensions are name/value pairs that carry more data to describe the metric value. For example, authentication type is a dimension for transactions. If you're interested in seeing only transactions that were authorized by using an account key, you can use the authentication dimension and filter on account key.
30
30
31
-
The **ResponseType** dimension reveals the success and failure rate, and the reasons for failure, such as timeouts, throttling, network errors, authorization failure, and so on. This information can give you a good insight as to why the performance of your applications may be suffering. For example, frequent throttling and timeout errors can indicate a high level of contention occurring for limited resources, and you might need to re-architect your system to the use the **Premium** rather than the **Standard** tier for your storage accounts. You might also need to spread the load across multiple storage accounts or select a different organization for any blob containers and tables that your application is using.
31
+
The **ResponseType** dimension reveals the success and failure rate, and the reasons for failure, such as timeouts, throttling, network errors, authorization failure, and so on. This information can give you a good insight as to why the performance of your applications might be suffering. For example, frequent throttling and timeout errors can indicate a high level of contention occurring for limited resources, and you might need to rearchitect your system to the use the **Premium** rather than the **Standard** tier for your storage accounts. You might also need to spread the load across multiple storage accounts or select a different organization for any blob containers and tables that your application is using.
32
32
33
33
## View and analyze metrics
34
34
@@ -72,7 +72,7 @@ az monitor metrics list --resource <resource-ID> --metric "Transactions" --inter
72
72
73
73
### Application code
74
74
75
-
You can get metric values by writing code that uses any of the Azure SDKs. The following example uses the [Azure SDK for .NET](/dotnet/azure/sdk/azure-sdk-for-dotnet) to get the average amount of Blob storage used in a storage account over a specified time period.
75
+
You can get metric values by writing code that uses any of the Software Development Kits (SDKs). The following example uses the [Azure SDK for .NET](/dotnet/azure/sdk/azure-sdk-for-dotnet) to get the average amount of Blob storage used in a storage account over a specified time period.
0 commit comments