fix and update

v-thepet · v-thepet · commit c828f7abc0ce · 2024-02-13T20:06:03.000-08:00
diff --git a/articles/storage/files/analyze-files-metrics.md b/articles/storage/files/analyze-files-metrics.md
@@ -320,85 +320,11 @@ Compared against the **Bandwidth by Max MiB/s**, we achieved 123 MiB/s at peak.
 
 :::image type="content" source="media/analyze-files-metrics/bandwidth-by-max-mibs.png" alt-text="Screenshot showing bandwidth by max MIBS." lightbox="media/analyze-files-metrics/bandwidth-by-max-mibs.png" border="false":::
 
-## Analyze logs
-
-You can access resource logs either as a blob in a storage account, as event data, or through Log Analytics queries. For information about how to find those logs, see [Azure resource logs](../../azure-monitor/essentials/resource-logs.md).
-
-All resource logs in Azure Monitor have the same fields 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 Azure Files resource logs is found in [Azure Files monitoring data reference](storage-files-monitoring-reference.md).
-
-To get the list of SMB and REST operations that are logged, see [Storage logged operations and status messages](/rest/api/storageservices/storage-analytics-logged-operations-and-status-messages).
-
-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 File 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.
-
-The [Activity log](../../azure-monitor/essentials/activity-log.md) is a type of platform log located in Azure that provides insight into subscription-level events. You can view it independently or route it to Azure Monitor Logs, where you can do much more complex queries using Log Analytics.  
-
-
-### Log authenticated requests
-
- The following types of authenticated requests are logged:
-
-- Successful requests
-- Failed requests, including timeout, throttling, network, authorization, and other errors
-- Requests that use Kerberos, NTLM or shared access signature (SAS), including failed and successful requests
-- Requests to analytics data (classic log data in the **$logs** container and classic metric data in the **$metric** tables)
-
-Requests made by the Azure Files service itself, such as log creation or deletion, aren't logged. For a full list of the SMB and REST requests that are logged, see [Storage logged operations and status messages](/rest/api/storageservices/storage-analytics-logged-operations-and-status-messages) and [Azure Files monitoring data reference](storage-files-monitoring-reference.md).
-
-### Sample Kusto queries
-
-If you send logs to Log Analytics, you can access those logs by using Azure Monitor log queries. For more information, see [Log Analytics tutorial](/azure/azure-monitor/logs/log-analytics-tutorial).
-
-Here are some queries that you can enter in the **Log search** bar to help you monitor your Azure Files. These queries work with the [new language](/azure/azure-monitor/logs/log-query-overview).
-
-> [!IMPORTANT]
-> When you select **Logs** from the storage account resource group menu, Log Analytics is opened with the query scope set to the current resource group. This means that log queries will only include data from that resource group. If you want to run a query that includes data from other resources or data from other Azure services, select **Logs** from the **Azure Monitor** menu. See [Log query scope and time range in Azure Monitor Log Analytics](/azure/azure-monitor/logs/scope) for details.
-
-Use these queries to help you monitor your Azure file shares:
-
-- View SMB errors over the last week
-
-```Kusto
-StorageFileLogs
-| where Protocol == "SMB" and TimeGenerated >= ago(7d) and StatusCode contains "-"
-| sort by StatusCode
-```
-- Create a pie chart of SMB operations over the last week
-
-```Kusto
-StorageFileLogs
-| where Protocol == "SMB" and TimeGenerated >= ago(7d) 
-| summarize count() by OperationName
-| sort by count_ desc
-| render piechart
-```
-
-- View REST errors over the last week
-
-```Kusto
-StorageFileLogs
-| where Protocol == "HTTPS" and TimeGenerated >= ago(7d) and StatusText !contains "Success"
-| sort by StatusText asc
-```
-
-- Create a pie chart of REST operations over the last week
-
-```Kusto
-StorageFileLogs
-| where Protocol == "HTTPS" and TimeGenerated >= ago(7d) 
-| summarize count() by OperationName
-| sort by count_ desc
-| render piechart
-```
-
-To view the list of column names and descriptions for Azure Files, see [StorageFileLogs](/azure/azure-monitor/reference/tables/storagefilelogs).
-
-For more information on how to write queries, see [Log Analytics tutorial](/azure/azure-monitor/logs/log-analytics-tutorial).
-
-## Next steps
+## Related content
 
 - [Monitor Azure Files](storage-files-monitoring.md)
-- [Create monitoring alerts for Azure Files](files-monitoring-alerts.md)
 - [Azure Files monitoring data reference](storage-files-monitoring-reference.md)
+- [Create monitoring alerts for Azure Files](files-monitoring-alerts.md)
 - [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource)
 - [Understand Azure Files performance](understand-performance.md)
 - [Troubleshoot ClientOtherErrors](/troubleshoot/azure/azure-storage/files-client-other-errors?toc=/azure/storage/files/toc.json)
diff --git a/articles/storage/files/files-monitoring-alerts.md b/articles/storage/files/files-monitoring-alerts.md
@@ -14,7 +14,7 @@ ms.custom: monitoring
 
 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/azure-monitor/alerts/alerts-metric-overview), [logs](/azure/azure-monitor/alerts/alerts-unified-log), and the [activity log](/azure/azure-monitor/alerts/activity-log-alerts). 
 
-To learn more about how to create an alert, see [Create or edit an alert rule](/azure/azure-monitor/alerts/alerts-create-new-alert-rule).
+This article shows you how to create alerts on throttling, capacity, egress, and high server latency. To learn more about creating alerts, see [Create or edit an alert rule](/azure/azure-monitor/alerts/alerts-create-new-alert-rule).
 
 For more information about alert types and alerts, see [Monitor Azure Files](storage-files-monitoring.md#alerts).
 
@@ -158,10 +158,10 @@ To create an alert for high server latency (average), follow these steps.
 
 8. Select **Review + create** to create the alert.
 
-## Next steps
+## Related content
 
 - [Monitor Azure Files](storage-files-monitoring.md)
-- [Analyze Azure Files metrics using Azure Monitor](analyze-files-metrics.md)
 - [Azure Files monitoring data reference](storage-files-monitoring-reference.md)
+- [Analyze Azure Files metrics](analyze-files-metrics.md)
 - [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource)
 - [Azure Storage metrics migration](../common/storage-metrics-migration.md)
diff --git a/articles/storage/files/storage-files-monitoring.md b/articles/storage/files/storage-files-monitoring.md
@@ -126,16 +126,31 @@ If your service has other logs that aren't resource logs or in the activity log,
 <!-- ANALYSIS SECTION START -------------------------------------->
 
 <!-- ## Analyze data. Required section. -->
-<a name="analyzing-logs"></a>
 [!INCLUDE [horz-monitor-analyze-data](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-analyze-data.md)]
 
 <!-- ### External tools. Required section. -->
 [!INCLUDE [horz-monitor-external-tools](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-external-tools.md)]
 
+### Analyze metrics for Azure Files
+
+Metrics for Azure Files are in these namespaces: 
+
+- Microsoft.Storage/storageAccounts
+- Microsoft.Storage/storageAccounts/fileServices
+
+For a list of available metrics for Azure Files, see [Azure Files monitoring data reference](storage-files-monitoring-reference.md).
+
+For a list of all Azure Monitor support metrics, which includes Azure Files, see [Azure Monitor supported metrics](/azure/azure-monitor/essentials/metrics-supported#microsoftstoragestorageaccountsfileservices).
+
+For detailed instructions on how to analyze Azure Files metrics such as availability, latency, and utilization, see [Analyze Azure Files metrics using Azure Monitor](analyze-files-metrics.md).
+
+<a name="analyzing-logs"></a>
 ### Analyze logs for Azure Files
 
 You can access resource logs either as a blob in a storage account, as event data, or through Log Analytics queries. For information about how to find those logs, see [Azure resource logs](/azure/azure-monitor/essentials/resource-logs).
 
+To get the list of SMB and REST operations that are logged, see [Storage logged operations and status messages](/rest/api/storageservices/storage-analytics-logged-operations-and-status-messages) and [Azure Files monitoring data reference](storage-files-monitoring-reference.md).
+
 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 File 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.
 
 #### Log authenticated requests
@@ -221,6 +236,8 @@ The following table lists common and recommended alert rules for Azure Files and
 |Metric | File share egress exceeds 500 GiB in one day. | Egress<br>Dimension name: FileShare (premium file share only) |
 |Metric | High server latency. | Success Server Latency<br>Dimension name: API Name, for example Read and Write API|
 
+For instructions on how to create alerts on throttling, capacity, egress, and high server latency, see [Create monitoring alerts for Azure Files](files-monitoring-alerts.md).
+
 <!-- ### Advisor recommendations -->
 [!INCLUDE [horz-monitor-advisor-recommendations](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-advisor-recommendations.md)]
 
