Editorial pass

stevenmatthew · stevenmatthew · commit a5c17a7c88e5 · 2023-03-27T01:43:02.000-07:00
diff --git a/articles/storage-mover/log-monitoring.md b/articles/storage-mover/log-monitoring.md
@@ -8,32 +8,20 @@ ms.topic: how-to
 ms.date: 03/20/2023
 ---
 
-# Monitoring Azure Storage Mover copy and job logs
+# How to enable Azure Storage Mover copy and job logs
 
-When you use a migration tool to move your critical data from on-premises sources to Azure destination targets, you want to monitor copy operations for outages and errors. Monitoring includes metrics and logs that provide visibility into the success of your migration. **Copy logs** and **Job run logs** are especially useful because they allow you to trace the migration result of individual files. Metrics relating to **Job run metrics** are also available, and can be analyzed to help pinpoint periods of low performance and other trends.
+When you use a migration tool to move your critical data from on-premises sources to Azure destination targets, you want to be able to monitor operations for potential issues. The data relating to the operations performed during your migration can be stored as either logs entries or metrics. When configured, Azure Storage Mover can provide **Copy logs** and **Job run logs**. These logs are especially useful because they allow you to trace the migration result of job runs and of individual files.
 
-Logs and metrics can be sent or streamed to the destinations listed in the following table. To ensure the security of data in transit, we strongly encourage you to configure Transport Layer Security (TLS). All destination endpoints support TLS 1.2.
+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.
 
-| Destination                           | Description |
-|:--------------------------------------|:------------|
-| **Log Analytics workspace**           | Metrics are converted to log form. This option might not be available for all resource types. Sending them to the Azure Monitor Logs store (which is searchable via Log Analytics) helps you to integrate them into queries, alerts, and visualizations with existing log data.
-| **Azure Storage account**             | Archiving logs and metrics to a Storage account is useful for audit, static analysis, or backup. Compared to using Azure Monitor Logs or a Log Analytics workspace, Storage is less expensive, and logs can be kept there indefinitely.  |
-| **Azure Event Hubs**                  | When you send logs and metrics to Event Hubs, you can stream data to external systems such as third-party SIEMs and other Log Analytics solutions.  |
-| **Azure Monitor partner integrations**| Specialized integrations can be made between Azure Monitor and other non-Microsoft monitoring platforms. Integration is useful when you're already using one of the partners.  |
+> [!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.
 
-This article describes the monitoring data reported from Azure Storage Mover, and how you can use the features of Azure Monitor to analyze errors during the migration. All other destinations are outside the scope of this article, but can be referenced in the [Diagnostic settings in Azure Monitor](/azure/azure-monitor/essentials/diagnostic-settings?WT.mc_id=Portal-Microsoft_Azure_Monitoring&tabs=portal) article.
+This article describes the steps involved to create an analytics workspace and to configure a diagnostic setting within a storage mover resource.
 
-## What is Azure Monitor?
+## Configuring Azure Log Analytics and Storage Mover
 
-Azure Storage Mover sends copy and job run monitoring data to Azure Monitor, Azure's full stack monitoring service. The Azure Monitor service provides a complete set of features to monitor your Azure resources and resources in other clouds and on-premises.
-
-One of Azure Monitor's most useful features is the Log Analytics tool. The Log Analytics tool is designed to help you monitor your migration projects by enabling you to  edit and run log queries against your copy and job logs.
-
-You can read more about Azure Monitor by visiting the [Azure Monitor overview](../azure-monitor/overview.md) article.
-
-## Configuring Azure Monitor and Storage Mover
-
-Before you can view the logs generated during your migration, you need to ensure that you've configured both Azure Monitor and your Storage Mover instance. This section briefly describes how to configure an Azure Monitor Log Analytics Workspace and Storage Mover diagnostic settings. After completing the following steps, you'll be able to query the data provided by your Storage Mover resource.
+This section briefly describes how to configure an Azure Monitor Log Analytics Workspace and Storage Mover diagnostic settings. After completing the following steps, you'll be able to query the data provided by your Storage Mover resource.
 
 ### Create a Log Analytics workspace
 
@@ -65,17 +53,9 @@ After your Storage Mover diagnostic setting has been saved, it will be reflected
 
 ## Analyzing logs
 
-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 logs, copy logs and job run logs. 
-
-Storage Mover generates two tables, StorageMoverCopyLogsFailed and StorageMoverJobRunLogs.
+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).
 
-The schema for StorageMoverCopyLogsFailed is found in [Azure Storage Copy log data reference](/azure/azure-monitor/reference/tables/StorageMoverCopyLogsFailed).
-
-The schema for StorageMoverJobRunLogs is found in [Azure Storage Job run log data reference](/azure/azure-monitor/reference/tables/StorageMoverJobRunLogs).
-
-Log entries are created only if there are requests made against the service endpoint. For example, if a storage account has activity in its file endpoint but not in its table or queue endpoints, only logs that pertain to the Azure Blob Storage 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.
+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).
 
 ### Sample Kusto queries
 
@@ -118,26 +98,12 @@ The sample queries provided below can be entered in the **Log search** bar to he
     | render piechart
     ```
 
-## Alerts
-
-Azure Monitor alerts proactively notify you when important conditions are found in your monitoring data. They allow you to identify and address issues in your system before your customers notice them. You can set alerts on [metrics](../azure-monitor/alerts/alerts-metric-overview.md), [logs](../azure-monitor/alerts/alerts-unified-log.md), and the [activity log](../azure-monitor/alerts/activity-log-alerts.md).
-
-The following table lists some example scenarios to monitor and the proper metric to use for the alert:
-
-| Scenario | Metric to use for alert |
-|-|-|
-| Storage Mover service is throttled. | Metric: Transactions<br>Dimension name: Response type |
-| Storage Mover requests are successful 99% of the time. | Metric: Availability<br>Dimension names: Geo type, API name, Authentication |
-| Storage Mover egress has exceeded 500 GiB in one day. | Metric: Egress<br>Dimension names: Geo type, API name, Authentication |
-
 ## Next steps
 
 Get started with any of these guides.
 
-| Guide | Description |
-|---|---|
-| [Getting started with Azure Metrics Explorer](../azure-monitor/essentials/metrics-getting-started.md) | A tour of Metrics Explorer. 
-| [Overview of Log Analytics in Azure Monitor](../azure-monitor/logs/log-analytics-overview.md) | A tour of Log Analytics. |
-| [Azure Monitor Metrics overview](../azure-monitor/essentials/data-platform-metrics.md) | The basics of metrics and metric dimensions  |
-| [Azure Monitor Logs overview](../azure-monitor/logs/data-platform-logs.md)| The basics of logs and how to collect and analyze them |
-| [Troubleshoot Storage Mover issues](log-monitoring.md)| Common performance issues and guidance about how to troubleshoot them. |
+- [Log Analytics workspaces](../azure-monitor/logs/log-analytics-workspace-overview)
+- [Azure Monitor Logs overview](../azure-monitor/logs/data-platform-logs.md)
+- [Diagnostic settings in Azure Monitor](../azure-monitor/essentials/diagnostic-settings?tabs=portal)
+- [Azure Storage Mover support bundle overview](troubleshooting.md)
+- [Troubleshooting Storage Mover job run error codes](status-code.md)
