Skip to content

Commit 55238d6

Browse files
committed
edit pass: two-azure-monitor-topics
1 parent fc71adc commit 55238d6

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/storage/common/monitor-storage.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ When you have critical applications and business processes that rely on Azure re
2222
The **Overview** page in the Azure portal for each storage resource includes a brief view of the resource usage, such as requests and hourly billing. This information is useful, but only a small amount of the monitoring data is available. Some of this data is collected automatically and is available for analysis as soon as you create the storage resource. You can enable additional types of data collection with some configuration.
2323

2424
## What is Azure Monitor?
25-
Azure Storage creates monitoring data by using [Azure Monitor](../../azure-monitor/overview.md), a full stack monitoring service in Azure. Azure Monitor provides a complete set of features to monitor your Azure resources and resources in other clouds and on-premises.
25+
Azure Storage creates monitoring data by using [Azure Monitor](../../azure-monitor/overview.md), which is a full stack monitoring service in Azure. Azure Monitor provides a complete set of features to monitor your Azure resources and resources in other clouds and on-premises.
2626

2727
To learn more about Azure Monitor, see [Monitoring Azure resources with Azure Monitor](../../azure-monitor/insights/monitor-azure-resource.md). The article describes the following subjects:
2828

@@ -38,26 +38,26 @@ The following sections build on this article by describing the specific data gat
3838

3939
Azure Storage collects the same kinds of monitoring data as other Azure resources, which are described in [Monitoring data from Azure resources](../../azure-monitor/insights/monitor-azure-resource.md#monitoring-data). For more information on the logs and metrics created by Azure Storage, see [Azure Storage monitoring data reference](monitor-storage-reference.md).
4040

41-
Metrics and logs in Azure Monitor support only Azure Resource Manager storage accounts. Azure Monitor doesn't support classic storage accounts. If you want to use metrics or logs on a classic storage account, you need to migrate to an Azure Resource Manager storage account. For more information, see [Migrate to Azure Resource Manager](https://docs.microsoft.com/azure/virtual-machines/windows/migration-classic-resource-manager-overview).
41+
Metrics and logs in Azure Monitor support only Azure Resource Manager storage accounts. Azure Monitor doesn't support classic storage accounts. If you want to use metrics or logs on a classic storage account, you need to migrate to an Azure Resource Manager storage account. See [Migrate to Azure Resource Manager](https://docs.microsoft.com/azure/virtual-machines/windows/migration-classic-resource-manager-overview).
4242

4343
You can continue using classic metrics and logs if you want to. In fact, classic metrics and logs are available in parallel with metrics and logs in Azure Monitor. The support remains in place until Azure Storage ends the service on legacy metrics and logs.
4444

4545
### Logs in Azure Monitor (preview)
4646

4747
Log entries are created only if there are requests made against the service endpoint. For example, if a storage account has activity in its blob endpoint but not in its table or queue endpoints, only logs that pertain to the blob service are created. Azure Storage logs contain detailed information about successful and failed requests to a storage service. This information can be used to monitor individual requests and to diagnose issues with a storage service. Requests are logged on a best-effort basis.
4848

49-
#### Logging authenticated requests
49+
#### Log authenticated requests
5050

5151
The following types of authenticated requests are logged:
5252

5353
- Successful requests
5454
- Failed requests, including timeout, throttling, network, authorization, and other errors
55-
- Requests that use a shared access signature or OAuth, including failed and successful requests
55+
- Requests that use a shared access signature (SAS) or OAuth, including failed and successful requests
5656
- Requests to analytics data (classic log data in the **$logs** container and class metric data in the **$metric** tables)
5757

58-
Requests made by the storage service itself, like log creation or deletion, aren't logged. For a full list of the logged data, see [Storage logged operations and status messages](/rest/api/storageservices/storage-analytics-logged-operations-and-status-messages) and [Storage log format](monitor-storage-reference.md).
58+
Requests made by the storage service itself, such as log creation or deletion, aren't logged. For a full list of the logged data, see [Storage logged operations and status messages](/rest/api/storageservices/storage-analytics-logged-operations-and-status-messages) and [Storage log format](monitor-storage-reference.md).
5959

60-
#### Logging anonymous requests
60+
#### Log anonymous requests
6161

6262
The following types of anonymous requests are logged:
6363

@@ -72,7 +72,7 @@ All other failed anonymous requests aren't logged. For a full list of the logged
7272

7373
Platform metrics and the Activity log are collected automatically, but you must create a diagnostic setting to collect resource logs or forward them outside of Azure Monitor. For the process to create a diagnostic setting by using the Azure portal, the Azure CLI, or PowerShell, see [Create diagnostic setting to collect platform logs and metrics in Azure](../../azure-monitor/platform/diagnostic-settings.md).
7474

75-
When you create a diagnostic setting, choose the type of storage for which you want to enable logs, such as a blob, queue, table, or file. If you create the diagnostic setting in the Azure portal, you can select the resource from a list. If you use PowerShell or the Azure CLI, you need to use the resource ID of the storage type. You can find the resource ID in the Azure portal by opening the **Properties** page of your storage account.
75+
When you create a diagnostic setting, choose the type of storage that you want to enable logs for, such as a blob, queue, table, or file. If you create the diagnostic setting in the Azure portal, you can select the resource from a list. If you use PowerShell or the Azure CLI, you need to use the resource ID of the storage type. You can find the resource ID in the Azure portal by opening the **Properties** page of your storage account.
7676

7777
You also have to specify the categories of operations for which you want to collect logs. The categories for Azure Storage are listed in this table.
7878

0 commit comments

Comments
 (0)