Skip to content

Commit 83143c5

Browse files
Update azure-monitor-agent-troubleshoot-windows-vm.md
1 parent 403d261 commit 83143c5

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-windows-vm.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,6 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
2424
```
2525
3. Wait for 10-15 minutes as extension maybe in transitioning status. If it still doesn't show up, [uninstall and install the extension](./azure-monitor-agent-manage.md) again and repeat the verification to see the extension show up.
2626
4. If not, check if you see any errors in extension logs located at `C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent` on your machine
27-
5. If none of the above helps, [file a ticket](#file-a-ticket) with **Summary** as 'AMA extension fails to install or provision' and **Problem type** as 'I need help with Azure Monitor Windows Agent'.
2827
2928
3. **Verify that the agent is running**:
3029
1. Check if the agent is emitting heartbeat logs to Log Analytics workspace using the query below. Skip if 'Custom Metrics' is the only destination in the DCR:
@@ -33,7 +32,6 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
3332
```
3433
2. If not, open Task Manager and check if 'MonAgentCore.exe' process is running. If it is, wait for 5 minutes for heartbeat to show up.
3534
3. If not, check if you see any errors in core agent logs located at `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\Configuration` on your machine
36-
4. If none of the above helps, [file a ticket](#file-a-ticket) with **Summary** as 'AMA extension provisioned but not running' and **Problem type** as 'I need help with Azure Monitor Windows Agent'.
3735
3836
4. **Verify that the DCR exists and is associated with the virtual machine:**
3937
1. If using Log Analytics workspace as destination, verify that DCR exists in the same physical region as the Log Analytics workspace.
@@ -44,12 +42,9 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
4442
- AMA can't access IMDS. Check if you see IMDS errors in `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\Tables\MAEventTable.tsf` file. If yes, [file a ticket](#file-a-ticket) with **Summary** as 'AMA cannot access IMDS' and **Problem type** as 'I need help configuring data collection from a VM'.
4543
3. Open Azure portal > select your data collection rule > Open **Configuration** : **Resources** from the pane on the left > You should see the virtual machine listed here
4644
4. If not listed, click 'Add' and select your virtual machine from the resource picker. Repeat across all DCRs.
47-
5. If none of the above helps, [file a ticket](#file-a-ticket) with **Summary** as 'DCR not found or associated' and **Problem type** as 'I need help configuring data collection from a VM'.
4845
4946
5. **Verify that agent was able to download the associated DCR(s) from AMCS service:**
5047
1. Check if you see the latest DCR downloaded at this location `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\mcs\configchunks`
51-
2. If not, [file a ticket](#file-a-ticket) with **Summary** as 'AMA unable to download DCR config' and **Problem type** as 'I need help with Azure Monitor Windows Agent'.
52-
5348
5449
## Issues collecting Performance counters
5550
1. Check that your DCR JSON contains a section for 'performanceCounters'. If not, fix your DCR. See [how to create DCR](./azure-monitor-agent-data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
@@ -65,8 +60,6 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
6560
<Counter>\PhysicalDisk(_Total)\Avg. Disk Queue Length</Counter>
6661
</CounterSet>
6762
```
68-
If there are no `CounterSet` nodes, then the DCR wasn't parsed correctly. [File a ticket](#file-a-ticket) with **Summary** as 'AMA unable to parse DCR config' and **Problem type** as 'I need help with Azure Monitor Windows Agent'.
69-
7063
7164
7265
### Issues using 'Custom Metrics' as destination
@@ -89,7 +82,6 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
8982
6. Collect logs by running the command `C:\Packages\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent\<version-number>\Monitoring\Agent\table2csv.exe C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\Tables\MaMetricsExtensionEtw.tsf`
9083
1. The command will generate the file 'MaMetricsExtensionEtw.csv'
9184
2. Open it and look for any Level 2 errors and try to fix them.
92-
7. If none of the above helps, [file a ticket](#file-a-ticket) with **Summary** as 'AMA unable to collect custom metrics' and **Problem type** as 'I need help with Azure Monitor Windows Agent'.
9385
9486
## Issues collecting Windows event logs
9587
1. Check that your DCR JSON contains a section for 'windowsEventLogs'. If not, fix your DCR. See [how to create DCR](./azure-monitor-agent-data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
@@ -106,4 +98,3 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
10698
</Column>
10799
</Subscription>
108100
```
109-
If there are no `Subscription`, nodes then the DCR wasn't parsed correctly. [File a ticket](#file-a-ticket) with **Summary** as 'AMA unable to parse DCR config' and **Problem type** as 'I need help with Azure Monitor Windows Agent'.

0 commit comments

Comments
 (0)