Skip to content

Commit 537da00

Browse files
author
Amson Liu
authored
Merge pull request #9354 from amsliu/v-liuamson-CI6622
New article for CI 6622.
2 parents cf45abb + e819c0b commit 537da00

File tree

2 files changed

+40
-0
lines changed

2 files changed

+40
-0
lines changed
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
title: Troubleshoot Performance Logs Not Populating in Azure Government
3+
description: Troubleshooting guide for performance logs not populating in Azure Government.
4+
ms.date: 07/24/2025
5+
ms.reviewer: v-liuamson; v-gsitser
6+
ms.service: azure-monitor
7+
ms.custom: Configure and Manage Log analytics tables
8+
---
9+
10+
# Troubleshoot performance logs not populating in Azure Government
11+
12+
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.
13+
14+
## Common issues and solutions
15+
16+
- **Issue**: Performance logs don't populate when you use DCR to set up alerts.
17+
- **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.
18+
- **Solution**: Set the alert scope to the Log Analytics workspace that's associated with the DCR.
19+
20+
### Instructions to resolve performance log issues
21+
22+
1. Navigate to the Azure portal, and select **Azure Monitor** on the services list.
23+
24+
2. Go to **Alerts** and select the option to either create an alert rule or edit an existing rule.
25+
26+
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.
27+
28+
4. Verify that the query runs successfully without errors by testing it directly in the Log Analytics workspace.
29+
30+
5. Save the alert configuration, and test it to verify that performance logs are now populating correctly.
31+
32+
## References
33+
34+
- [Azure Monitor documentation](/azure/azure-monitor/)
35+
- [Log Analytics workspace overview](/azure/azure-monitor/logs/log-analytics-workspace-overview)
36+
- [Create and manage alerts in Azure](/azure/azure-monitor/alerts/alerts-overview)
37+
38+
If the issue persists after you follow these steps, open a support case for further assistance.

support/azure/azure-monitor/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -121,6 +121,8 @@ items:
121121
href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-table-creation-errors.md
122122
- name: Troubleshoot custom log table creation in Azure
123123
href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-log-table-creation.md
124+
- name: Troubleshoot performance logs not populating in Azure Government
125+
href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-performance-logs-not-populating.md
124126
- name: Log Analytics workspaces
125127
items:
126128
- name: Error code 0x80090016 - keyset doesn't exist

0 commit comments

Comments
 (0)