Skip to content

Commit d54b7a2

Browse files
author
amsliu
committed
New article for CI 6622
1 parent 24a4ff2 commit d54b7a2

File tree

3 files changed

+50
-10
lines changed

3 files changed

+50
-10
lines changed

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/new.md

Lines changed: 0 additions & 8 deletions
This file was deleted.
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
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/16/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+
When setting up alerts for VM insights using Data Collection Rules (DCR) in Azure Government, users may encounter issues where performance logs fail to populate. This problem typically arises when creating alerts through DCR, as opposed to executing queries directly in the Log Analytics workspace.
13+
14+
## Common Issues and Solutions
15+
16+
- **Issue**: Alerts fail to populate performance logs when using DCR.
17+
- **Root Cause**: The custom KQL query is executed against the DCR, which lacks access to necessary data tables. The scope defaults to DCR, preventing data retrieval.
18+
- **Solution**: Set the alert scope to the Log Analytics workspace associated with the DCR.
19+
20+
### Step-by-Step Instructions to Resolve Performance Log Issues
21+
22+
#### 1. Access Azure Monitor
23+
24+
- Navigate to the Azure portal and select **Azure Monitor** from the services list.
25+
26+
#### 2. Create or Edit an Alert
27+
28+
- Go to **Alerts** and choose to create a new alert rule or edit an existing one.
29+
30+
#### 3. Set the Correct Scope
31+
32+
- In the alert rule configuration, ensure the **Scope** is set to the Log Analytics workspace, not the DCR. This allows the query to access the necessary data tables.
33+
34+
#### 4. Verify Query Execution
35+
36+
- Test the query directly in the Log Analytics workspace to ensure it runs successfully without errors.
37+
38+
#### 5. Save and Test the Alert
39+
40+
- Save the alert configuration and test it to confirm that performance logs are now populating correctly.
41+
42+
## Reference
43+
44+
- [Azure Monitor Documentation](https://learn.microsoft.com/azure/azure-monitor/)
45+
- [Log Analytics Workspace Overview](https://learn.microsoft.com/azure/azure-monitor/logs/log-analytics-workspace-overview)
46+
- [Creating and Managing Alerts in Azure](https://learn.microsoft.com/azure/azure-monitor/alerts/alerts-overview)
47+
48+
If the issue persists after following the solution steps, please open a support case for further assistance.

support/azure/azure-monitor/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -95,8 +95,8 @@ items:
9595
items:
9696
- name: Configure and Manage Log analytics tables
9797
items:
98-
- name: New
99-
href: log-analytics/configure-and-manage-log-analytics-tables/new.md
98+
- name: Troubleshoot Performance Logs Not Populating in Azure Government
99+
href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-performance-logs-not-populating.md
100100
- name: Log Analytics workspaces
101101
items:
102102
- name: Error code 0x80090016 - keyset doesn't exist

0 commit comments

Comments
 (0)