Merge pull request #9410 from MicrosoftDocs/main

Auto push to live 2025-07-24 18:07:53

Author: Simonx Xu

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-log-table-creation.md

@@ -0,0 +1,39 @@
+---
+title: Troubleshoot Custom Log Table Creation in Azure
+description: Troubleshooting guide for custom log table creation in Azure.
+ms.date: 07/23/2025
+ms.reviewer: v-liuamson; v-gsitser
+ms.service: azure-monitor
+ms.custom: Configure and Manage Log analytics tables
+---
+
+# Troubleshoot custom log table creation in Azure
+
+Users might receive an error message that states "Cannot read properties of undefined (reading length)" when they try to create a custom log table by using a JSON file in Microsoft Azure. This issue typically occurs during the final step of table creation even though the JSON file is valid. If you understand the root cause of the issue and follow the correct steps, you can resolve this issue efficiently.
+
+## Common issues and solutions
+
+- Error: Cannot read properties of undefined (reading length): This error often indicates an issue that affects the JSON structure or the DCR configuration. Doublecheck both for accuracy.
+
+- No Data Ingestion: Verify that the data source is correctly set up to collect log files. The data source type should be **Custom (Log files)**, and the stream declaration should follow the format `Custom-<TableName>`.
+
+### Instructions to resolve the issue
+
+1. Make sure that the JSON file that's used is correctly formatted and valid. Use a JSON validator tool to verify this.
+
+2. Create a new data collection rule (DCR):
+   1. Navigate to the Azure portal > **Log Analytics Workspace**.
+   1. Create a DCR specifically for the custom log table. Avoid using an existing DCR that collects other types of data because this action can cause configuration conflicts.
+
+3. Follow the steps that are outlined in the [Azure documentation](/azure/azure-monitor/vm/data-collection-log-json#create-custom-table) to create the custom table by using a PowerShell script. This method allows you to specify the file pattern and verify the DCR configuration after the creation is finished.
+
+4. To be able to perform these actions, make sure that you have at least the Contributor role in the relevant Azure Workspace.
+
+5. If the issue persists, try to refresh the Azure portal to make sure that all settings are updated.
+
+## Reference
+
+- [Create Custom Table in Azure](/azure/azure-monitor/vm/data-collection-log-json#create-custom-table)
+- [Data Collection Rule Best Practices](/azure/azure-monitor/data-collection/data-collection-rule-best-practices)
+
+If the issue persists after you follow these steps, please open a support case for further assistance.

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-table-creation-errors.md

@@ -0,0 +1,44 @@
+---
+title: Troubleshoot Custom Table Creation Errors in Azure
+description: Troubleshooting guide for custom table creation errors in Azure.
+ms.date: 07/23/2025
+ms.reviewer: v-liuamson; v-gsitser
+ms.service: azure-monitor
+ms.custom: Configure and Manage Log analytics tables
+---
+
+# Troubleshoot custom table creation errors in Azure
+
+Users might receive an error message that indicates that properties of undefined data can't be read when they try to create a custom table in Microsoft Azure. This issue can occur because of temporary glitches or misconfigurations. This article helps you determine the root cause of the errors and troubleshoot this issue efficiently.
+
+## Common issues and solutions
+
+- **Temporary Glitches**: Often, errors are temporary. You might be able to resolve the issue by trying the process again after a short time.
+- **Configuration Errors**: Make sure that all configurations and permissions are correctly set in Azure.
+
+### Instructions to resolve custom table creation errors
+
+1. Verify JSON file validity:
+   1. Make sure that the JSON file that's used for table creation is correctly formatted and contains all the required fields.
+   1. Use tools such as *JSONLint* to validate the JSON structure.
+
+2. Check the Azure logs:
+   1. Navigate to **Azure Monitor**, and access the **Logs** section.
+   1. Review the ARM logs for any error messages that are related to the custom table creation process.
+
+3. Try again to create tables:
+   1. Run the table creation process again by using the Azure portal or Azure CLI.
+   1. If the error persists, consider using a different browser or clearing the browser cache.
+
+4. Collect diagnostic information:
+   1. Gather HAR files and console logs to identify any front-end issues.
+   1. Use the Azure portal to capture network activity during the table creation process.
+
+5. Consult Azure documentation: For detailed guidance on custom tables, see [Manage tables in a Log Analytics workspace](/azure/azure-monitor/logs/manage-logs-tables?tabs=azure-portal).
+
+## References
+
+- [Azure Monitor Overview](/azure/azure-monitor/fundamentals/overview)
+- [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request)
+
+If the issue persists after you following these steps, open a support case for further assistance.

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-performance-logs-not-populating.md

@@ -0,0 +1,38 @@
+---
+title: Troubleshoot Performance Logs Not Populating in Azure Government
+description: Troubleshooting guide for performance logs not populating in Azure Government.
+ms.date: 07/24/2025
+ms.reviewer: v-liuamson; v-gsitser
+ms.service: azure-monitor
+ms.custom: Configure and Manage Log analytics tables
+---
+
+# Troubleshoot performance logs not populating in Azure Government
+
+Users might experience issues if performance logs don't populate in Azure Government when they set up alerts for virtual machine (VM) insights by using Data Collection Rules (DCR). This issue typically occurs when users create alerts through DCR instead of running queries directly in the Log Analytics workspace.
+
+## Common issues and solutions
+
+- **Issue**: Performance logs don't populate when you use DCR to set up alerts.
+- **Root cause**: The custom KQL query is run against the DCR, but the DCR can't access the required data tables. In this situation, the alert scope defaults to DCR. This action prevents data retrieval.
+- **Solution**: Set the alert scope to the Log Analytics workspace that's associated with the DCR.
+
+### Instructions to resolve performance log issues
+
+1. Navigate to the Azure portal, and select **Azure Monitor** on the services list.
+
+2. Go to **Alerts** and select the option to either create an alert rule or edit an existing rule.
+
+3. In the alert rule configuration, make sure that the **Scope** value is set to the Log Analytics workspace, not to the DCR. This setting enables the query to access the required data tables.
+
+4. Verify that the query runs successfully without errors by testing it directly in the Log Analytics workspace.
+
+5. Save the alert configuration, and test it to verify that performance logs are now populating correctly.
+
+## References
+
+- [Azure Monitor documentation](/azure/azure-monitor/)
+- [Log Analytics workspace overview](/azure/azure-monitor/logs/log-analytics-workspace-overview)
+- [Create and manage alerts in Azure](/azure/azure-monitor/alerts/alerts-overview)
+
+If the issue persists after you follow these steps, open a support case for further assistance.

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/understand-and-mitigate-high-data-consumption-log-analytics.md

@@ -0,0 +1,45 @@
+---
+title: Understand and Mitigate High Data Consumption in Log Analytics
+description: Provides instructions to resolve high data usage in Log Analytics.
+ms.date: 07/24/2025
+ms.reviewer: v-liuamson; v-gsitser
+ms.service: azure-monitor
+ms.custom: Configure and Manage Log analytics tables
+---
+
+# Understand and mitigate high data consumption in Log Analytics
+
+This article discusses high data consumption that occurs in Log Analytics workspaces, and focuses on tables such as `AzureDiagnostics`. This article also provides insights into the costs that are associated with data usage, and offers steps to optimize and reduce these costs.
+
+## Common issues and solutions
+
+- **Data retention**: Make sure that data retention settings are configured appropriately to avoid unnecessary storage costs.
+- **Data filtering**: Implement data filtering to collect only necessary data and reduce the volume of data ingested.
+
+### Instructions to resolve high data usage
+
+1. Identify high data tables:
+
+   1. Use the `AzureDiagnostics` table to determine which listed references are sending large amounts of data.
+   1. To identify the reference that's contributing to high data usage, run the following query in your Log Analytics workspace:
+
+        ```plaintext
+        AzureDiagnostics | distinct _ResourceId
+        ```
+
+2. Review the diagnostic settings:
+
+   1. Navigate to the diagnostic settings of the identified reference.
+   1. Remove unnecessary diagnostic settings if the data isn't required. This step stops the data from being sent to the AzureDiagnostics table.
+
+3. Review the articles in the ["References" section](#references) to understand the costs that are associated with your Log Analytics workspace.
+
+4. To optimize data usage and reduce costs, follow the best practices that are outlined in the "References" section.
+
+## References
+
+- [Understand Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/)
+- [Best Practices for Cost Management](/azure/azure-monitor/fundamentals/best-practices-cost)
+- [Cost Management for Logs](/azure/azure-monitor/logs/cost-logs)
+
+If the issue persists after you follow the solution steps, open a support case for further assistance.

support/azure/azure-monitor/toc.yml

@@ -113,6 +113,16 @@ items:
       href: app-insights/agent/change-analysis-troubleshoot.md
 - name: Log Analytics
   items:
+  - name: Configure and Manage Log analytics tables
+    items:
+    - name: Understand and mitigate high data consumption in Log Analytics
+      href: log-analytics/configure-and-manage-log-analytics-tables/understand-and-mitigate-high-data-consumption-log-analytics.md
+    - name: Troubleshoot custom table creation errors in Azure
+      href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-table-creation-errors.md
+    - name: Troubleshoot custom log table creation in Azure
+      href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-log-table-creation.md
+    - name: Troubleshoot performance logs not populating in Azure Government
+      href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-performance-logs-not-populating.md
   - name: Log Analytics workspaces
     items:
     - name: Error code 0x80090016 - keyset doesn't exist

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-managed-identities.md

@@ -183,7 +183,22 @@ This issue often occurs in the following situations:
 
 When the managed identity changes, the File Sync agent tries to use the new identity, but the Azure File Sync service is still configured to authorize the previous one. This mismatch causes requests to fail with the `ECS_E_AUTH_IDENTITY_NOT_FOUND` error.
 
-To resolve this issue, run the following PowerShell command:
+To resolve this issue: 
+
+First, ensure the server is configured to use a managed identity. 
+
+You can verify this by:
+- Checking the **Settings** > **Managed identities** details in your storage sync service, or
+- Running the following PowerShell command:
+
+```powershell
+Get-AzStorageSyncServer -ResourceGroupName <ResourceGroupName> -StorageSyncServiceName <StorageSyncServiceName>
+```
+> [!NOTE]
+> This error can occur whether the server is using managed identity (MI) or certificate-based authentication, so confirming the identity type is important.
+
+
+If the server is using managed identity and the identity has changed, run the following command to update the server registration:
 
 ```powershell
 Set-AzStorageSyncServer -ResourceGroupName <ResourceGroupName> -StorageSyncServiceName <StorageSyncServiceName> -Identity