You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-performance-logs-not-populating.md
+10-15Lines changed: 10 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,25 +19,20 @@ When setting up alerts for VM insights using Data Collection Rules (DCR) in Azur
19
19
20
20
### Step-by-Step Instructions to Resolve Performance Log Issues
21
21
22
-
#### 1. Access Azure Monitor
22
+
1.**Access Azure Monitor**:
23
+
- Navigate to the Azure portal and select **Azure Monitor** from the services list.
23
24
24
-
- Navigate to the Azure portal and select **Azure Monitor** from the services list.
25
+
2.**Create or Edit an Alert**:
26
+
- Go to **Alerts** and choose to create a new alert rule or edit an existing one.
25
27
26
-
#### 2. Create or Edit an Alert
28
+
3.**Set the Correct Scope**:
29
+
- 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.
27
30
28
-
- Go to **Alerts** and choose to create a new alert rule or edit an existing one.
31
+
4.**Verify Query Execution**:
32
+
- Test the query directly in the Log Analytics workspace to ensure it runs successfully without errors.
29
33
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.
34
+
5.**Save and Test the Alert**:
35
+
- Save the alert configuration and test it to confirm that performance logs are now populating correctly.
0 commit comments