Skip to content

Commit e3357bd

Browse files
committed
Editorial pass
1 parent a5c17a7 commit e3357bd

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/storage-mover/log-monitoring.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Both the copy and job run logs can be sent to an Azure Analytics Workspace. Anal
1717
> [!IMPORTANT]
1818
> Before you can access migrations's log data, you need to ensure that you've created an Azure Analytics Workspace and configured your Storage Mover instance to use it. It's important to complete the steps described within this article before running your migration jobs to collect the resulting data. Any migration log data generated prior to configuration will not be accessible.
1919
20-
This article describes the steps involved to create an analytics workspace and to configure a diagnostic setting within a storage mover resource.
20+
This article describes the steps involved in creating an analytics workspace and to configure a diagnostic setting within a storage mover resource.
2121

2222
## Configuring Azure Log Analytics and Storage Mover
2323

@@ -59,11 +59,11 @@ Storage Mover generates two tables, StorageMoverCopyLogsFailed and StorageMoverJ
5959

6060
### Sample Kusto queries
6161

62-
After you send logs to Log Analytics, you can access those logs by using Azure Monitor log queries. For more information on these queries, refer to the [Log Analytics tutorial](../azure-monitor/logs/log-analytics-tutorial.md).
62+
After you send logs to Log Analytics, you can access those logs by using Azure Monitor log queries. For more information, see the [Log Analytics tutorial](../azure-monitor/logs/log-analytics-tutorial.md).
6363

64-
The sample queries provided below can be entered in the **Log search** bar to help you monitor your migration. These queries work with the [new language](../azure-monitor/logs/log-query-overview.md).
64+
The following sample queries provided can be entered in the **Log search** bar to help you monitor your migration. These queries work with the [new language](../azure-monitor/logs/log-query-overview.md).
6565

66-
- To list all the files which failed to copy from a specific job run within the last 30 days.
66+
- To list all the files that failed to copy from a specific job run within the last 30 days.
6767

6868
```kusto
6969
StorageMoverCopyLogsFailed

0 commit comments

Comments
 (0)