added log analytis content

Author: stevenmatthew

articles/storage-mover/log-monitoring.md

@@ -15,7 +15,7 @@ When you use a migration tool to move your critical data from on-premises source
 Both the copy and job run logs can be sent to an Azure Analytics Workspace. Analytics workspaces are storage units where log data generated by Azure services are stored. Log Analytics is also integrated into the Storage Mover portal experience. This integration allows you to create and run log queries from multiple logs and interactively analyze their results.
 
 > [!IMPORTANT]
-> 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.
+> Before you can access your migration'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.
 
 This article describes the steps involved in creating an analytics workspace and to configure a diagnostic setting within a storage mover resource.
 
@@ -55,7 +55,20 @@ After your Storage Mover diagnostic setting has been saved, it will be reflected
 
 All resource logs in Azure Monitor have the same fields, and are followed by service-specific fields. The common schema is outlined in [Azure Monitor resource log schema](../azure-monitor/essentials/resource-logs-schema.md).
 
-Storage Mover generates two tables, StorageMoverCopyLogsFailed and StorageMoverJobRunLogs. The schema for **StorageMoverCopyLogsFailed** is found in the [Azure Storage Copy log data reference](/azure/azure-monitor/reference/tables/StorageMoverCopyLogsFailed), and the schema for **StorageMoverJobRunLogs** is found in [Azure Storage Job run log data reference](/azure/azure-monitor/reference/tables/StorageMoverJobRunLogs).
+Storage Mover generates two tables, StorageMoverCopyLogsFailed and StorageMoverJobRunLogs. The schema for **StorageMoverCopyLogsFailed** is found in the [Azure Storage Copy log data reference](/azure/azure-monitor/reference/tables/StorageMoverCopyLogsFailed), and the schema for **StorageMoverJobRunLogs** is found in the [Azure Storage Job run log data reference](/azure/azure-monitor/reference/tables/StorageMoverJobRunLogs).
+
+You 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." :::
+
+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.
+
+:::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." :::
+
+```kusto
+    StorageMoverCopyLogsFailed 
+    | where TimeGenerated > ago(30d) and JobRunName == "[job run ID]"
+```
 
 ### Sample Kusto queries
 
@@ -66,8 +79,8 @@ 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]"
+    StorageMoverCopyLogsFailed
+    | where TimeGenerated > ago(30d) 
     ```
 
 - To list the 10 most common copy log error codes over the last seven days.