Skip to content

Commit 1e01669

Browse files
author
amsliu
committed
formatting update
1 parent d54b7a2 commit 1e01669

File tree

1 file changed

+10
-15
lines changed

1 file changed

+10
-15
lines changed

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

Lines changed: 10 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -19,25 +19,20 @@ When setting up alerts for VM insights using Data Collection Rules (DCR) in Azur
1919

2020
### Step-by-Step Instructions to Resolve Performance Log Issues
2121

22-
#### 1. Access Azure Monitor
22+
1. **Access Azure Monitor**:
23+
- Navigate to the Azure portal and select **Azure Monitor** from the services list.
2324

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.
2527

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.
2730

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.
2933

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.
4136

4237
## Reference
4338

0 commit comments

Comments
 (0)