Skip to content

Commit fc28eb4

Browse files
committed
Adding 'not' to sentence
1 parent dae08ca commit fc28eb4

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

articles/azure-monitor/vm/vminsights-troubleshoot.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -9,17 +9,17 @@ ms.custom: references_regions
99

1010
---
1111

12-
# Troubleshoot VM insights
12+
# Troubleshoot VM Insights
1313

1414
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.
1515

1616
## Can't enable VM Insights on a machine
1717

1818
When you onboard an Azure virtual machine (VM) from the Azure portal, the following actions occur:
1919

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

2424
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.
2525

@@ -155,8 +155,8 @@ Heartbeat
155155

156156
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:
157157

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)
160160

161161
## Virtual machine doesn't appear in the Map view
162162

@@ -178,13 +178,13 @@ Use the log query in the [Performance view has no data](#performance-view-has-no
178178

179179
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:
180180

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 |
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 |
185185

186186
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.
187187

188188
## Related content
189189

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

Comments
 (0)