Skip to content

Commit 83ef0f5

Browse files
committed
Fixing some things
1 parent f146961 commit 83ef0f5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/storage/common/monitor-storage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ You can continue using classic metrics and logs if you want to. In fact, classic
4444

4545
### Logs in Azure Monitor
4646

47-
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 pertaining to the blob service will be created.
47+
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 pertaining to the blob service will be 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

4949
#### Logging authenticated requests
5050

@@ -398,7 +398,7 @@ No, Azure Compute supports the metrics on disks. See [article](https://azure.mic
398398
399399
## Next steps
400400
401-
- [Azure Storage monitoring data reference](monitor-storage-reference.md) for a reference of the logs and metrics created by Azure Cosmos DB.
401+
- [Azure Storage monitoring data reference](monitor-storage-reference.md) for a reference of the logs and metrics created by Azure Storage.
402402
- [Monitoring Azure resources with Azure Monitor](../../azure-monitor/insights/monitor-azure-resource.md) for details on monitoring Azure resources.
403403
- [Azure Storage metrics migration](./storage-metrics-migration.md)
404404

0 commit comments

Comments
 (0)