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: articles/azure-monitor/vm/vminsights-troubleshoot.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,17 +9,17 @@ ms.custom: references_regions
9
9
10
10
---
11
11
12
-
# Troubleshoot VM insights
12
+
# Troubleshoot VM Insights
13
13
14
14
This article provides troubleshooting information to help you with problems that you might experience when you try to enable or use the VM Insights feature in Azure Monitor.
15
15
16
16
## Can't enable VM Insights on a machine
17
17
18
18
When you onboard an Azure virtual machine (VM) from the Azure portal, the following actions occur:
19
19
20
-
- A default Log Analytics workspace is created if you selected that option.
21
-
- The Azure Monitor Agent is installed on the virtual machine through an extension, if the agent is already installed.
22
-
- The Dependency Agent is installed on the virtual machine through an extension, if it's required.
20
+
* A default Log Analytics workspace is created if you selected that option.
21
+
* The Azure Monitor Agent is installed on the virtual machine through an extension, if the agent isn't already installed.
22
+
* The Dependency Agent is installed on the virtual machine through an extension, if it's required.
23
23
24
24
During the onboarding process, each of these steps is verified and a notification status appears in the portal. Configuration of the workspace and the agent installation typically takes 5 to 10 minutes. It takes another 5 to 10 minutes for data to become available to view in the portal.
25
25
@@ -155,8 +155,8 @@ Heartbeat
155
155
156
156
If no data appears or if the computer didn't send a heartbeat recently, you might have problems with your agent. For agent troubleshooting information, see these articles:
157
157
158
-
-[Troubleshoot issues with the Log Analytics agent for Windows](../agents/agent-windows-troubleshoot.md)
159
-
-[Troubleshoot issues with the Log Analytics agent for Linux](../agents/agent-linux-troubleshoot.md)
158
+
*[Troubleshoot issues with the Log Analytics agent for Windows](../agents/agent-windows-troubleshoot.md)
159
+
*[Troubleshoot issues with the Log Analytics agent for Linux](../agents/agent-linux-troubleshoot.md)
160
160
161
161
## Virtual machine doesn't appear in the Map view
162
162
@@ -178,13 +178,13 @@ Use the log query in the [Performance view has no data](#performance-view-has-no
178
178
179
179
If the virtual machine is in the **Map** view and the Dependency Agent is installed and running, but the kernel driver didn't load, check the log file at the following locations:
180
180
181
-
| Operating system | Log |
182
-
|:---|:---|
183
-
| Windows | C:\Program Files\Microsoft Dependency Agent\logs\wrapper.log |
184
-
| Linux | /var/opt/microsoft/dependency-agent/log/service.log |
| Windows | C:\Program Files\Microsoft Dependency Agent\logs\wrapper.log |
184
+
| Linux | /var/opt/microsoft/dependency-agent/log/service.log|
185
185
186
186
The last lines of the file should indicate why the kernel didn't load. For example, the kernel might not be supported on Linux if you updated your kernel.
187
187
188
188
## Related content
189
189
190
-
- For more information on installing VM Insights agents, see [Enable VM Insights overview](vminsights-enable-overview.md)
190
+
* For more information on installing VM Insights agents, see [Enable VM Insights overview](vminsights-enable-overview.md)
0 commit comments