editorial edits per publishing team

Author: stevenmatthew

articles/storage-mover/log-monitoring.md

@@ -44,7 +44,7 @@ Storage Mover collects copy and job logs, and stores the information in an Azure
 
 Enter **Log Analytics** in the search box and select **Log Analytics workspace**. In the content pane, select either **Create** or **Create log analytics workspace** to create a workspace. Provide values for the **Subscription**, **Resource Group**, **Name**, and **Region** fields, and select **Review + Create**.
 
-:::image type="content" source="media/log-monitoring/workspace-create-sml.png" lightbox="media/log-monitoring/workspace-create-lrg.png" alt-text="This image illustrates the methods of creating an Azure Analytics Workspace." :::
+:::image type="content" source="media/log-monitoring/workspace-create-sml.png" lightbox="media/log-monitoring/workspace-create-lrg.png" alt-text="Screen capture illustrating the methods of creating an Azure Analytics Workspace." :::
 
 You can get more detailed information about Log Analytics and its features by visiting the [Log Analytics overview](/azure/azure-monitor/logs/log-analytics-overview) article. If you prefer to view a tutorial, you can visit the [Log Analytics tutorial](/azure/azure-monitor/logs/log-analytics-tutorial) instead.
 
@@ -54,15 +54,15 @@ After an analytics workspace has been created, you can specify it as the destina
 
 There are two options for configuring Storage Mover to send logs to your analytics workspace. First, you can configure diagnostic settings during the initial deployment of your top-level Storage Mover resource. The following example shows how to specify diagnostic settings in the Azure portal during Storage Mover resource creation.
 
-:::image type="content" source="media/log-monitoring/monitoring-configure-sml.png" lightbox="media/log-monitoring/monitoring-configure-lrg.png" alt-text="This image highlights the ability to enable monitoring during initial deployment." :::
+:::image type="content" source="media/log-monitoring/monitoring-configure-sml.png" lightbox="media/log-monitoring/monitoring-configure-lrg.png" alt-text="Screen capture highlighting the ability to enable monitoring during initial deployment." :::
 
 You may also choose to add a diagnostic setting to a Storage Mover resource after it's been deployed. To add the diagnostic setting, navigate to the Storage Mover resource. In the menu pane, select **Diagnostic settings** and then select **Add diagnostic setting** as shown in the following example.
 
-:::image type="content" source="media/log-monitoring/diagnostic-settings-sml.png" lightbox="media/log-monitoring/diagnostic-settings-lrg.png" alt-text="This image highlights the ability to add a diagnostic setting after deployment." :::
+:::image type="content" source="media/log-monitoring/diagnostic-settings-sml.png" lightbox="media/log-monitoring/diagnostic-settings-lrg.png" alt-text="Screen capture highlighting the ability to add a diagnostic setting after deployment." :::
 
 In the **Diagnostic setting** pane, provide a value for the **Diagnostic setting name**. Within the **Logs** group, select one or more log categories to be collected. You may also select the **Job runs** option within the **Metrics** group to view the results of your individual job runs. Within the **Destination details** group, select **Send to Log Analytics workspace**, the name of your subscription, and the name of the Log Analytics workspace to collect your log data. Finally, select **Save** to add your new diagnostic setting. You can view the image provided as a reference.
 
-:::image type="content" source="media/log-monitoring/setting-add-sml.png" lightbox="media/log-monitoring/setting-add-lrg.png" alt-text="This image illustrates the location of the fields required to add a Diagnostic Setting to an existing Storage Mover resource." :::
+:::image type="content" source="media/log-monitoring/setting-add-sml.png" lightbox="media/log-monitoring/setting-add-lrg.png" alt-text="Screen capture illustrating the location of the fields required to add a Diagnostic Setting to an existing Storage Mover resource." :::
 
 After your Storage Mover diagnostic setting has been saved, it will be reflected on the Diagnostic settings screen within the **Diagnostic settings** table.
 
@@ -74,11 +74,11 @@ Storage Mover generates two tables, StorageMoverCopyLogsFailed and StorageMoverJ
 
 Your log data is integrated into Storage Mover's Azure portal user interface (UI) experience. To access your log data, migrate to your top-level storage mover resource and select **Logs** from within the **Monitoring** group in the navigation pane. Close the initial **Welcome to Log Analytics** window displayed in the main content pane as shown in the following example.
 
-:::image type="content" source="media/log-monitoring/logs-splash-sml.png" lightbox="media/log-monitoring/logs-splash-lrg.png" alt-text="This image illustrates the selections required to open the Logs pane and close the splash screen." :::
+:::image type="content" source="media/log-monitoring/logs-splash-sml.png" lightbox="media/log-monitoring/logs-splash-lrg.png" alt-text="Screen capture illustrating the selections required to open the Logs pane and close the splash screen." :::
 
 After the **Welcome** window is closed within the main content pane, the **New Query** window is displayed. In the schema and filter pane, ensure that the **Tables** object is selected and that the **StorageMoverCopyLogsFailed** and **StorageMoverJobRunLogs** tables are visible. Using Kusto Query Language (KQL) queries, you can begin extracting log data from the tables displayed within the schema and filter pane. Enter your query into the query editing field and select **Run** as shown in the following screen capture. A simple query example is also provided used to retrieve details on any failed copy operations from the previous 60 days.
 
-:::image type="content" source="media/log-monitoring/logs-query-sml.png" lightbox="media/log-monitoring/logs-query-lrg.png" alt-text="This image identifies the panes within the Log Analytics schema and filter page." :::
+:::image type="content" source="media/log-monitoring/logs-query-sml.png" lightbox="media/log-monitoring/logs-query-lrg.png" alt-text="Screen capture identifying the panes within the Log Analytics schema and filter page." :::
 
 ```kusto
     StorageMoverCopyLogsFailed 
@@ -93,10 +93,10 @@ The following sample queries provided can be entered in the **Log search** bar t
 
 - To list all the files that failed to copy from a specific job run within the last 30 days.
 
-```kusto
-    StorageMoverCopyLogsFailed 
-    | where TimeGenerated > ago(30d) and JobRunName == "[job run ID]"
-```
+    ```kusto
+        StorageMoverCopyLogsFailed 
+        | where TimeGenerated > ago(30d) and JobRunName == "[job run ID]"
+    ```
 
 - To list the 10 most common copy log error codes over the last seven days.