Skip to content

Commit f47a15a

Browse files
committed
fixing broken bookmark
1 parent 480d5b9 commit f47a15a

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/azure-monitor/vm/vminsights-enable-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ If you associate a data collection rule with the Map feature enabled to a machin
117117
118118
- You must remove the Log Analytics agent yourself from any machines that are using it. Before you do this step, ensure that the machine isn't relying on any other solutions that require the Log Analytics agent. For more information, see [Migrate to Azure Monitor Agent from Log Analytics agent](../agents/azure-monitor-agent-migration.md).
119119

120-
- After you verify that no Log Analytics agents are still connected to your Log Analytics workspace, you can [remove the VM Insights solution from the workspace](vminsights-configure-workspace.md#remove-vminsights-solution-from-a-workspace). It's no longer needed.
120+
- After you verify that no Log Analytics agents are still connected to your Log Analytics workspace, you can [remove the VM Insights solution from the workspace](vminsights-configure-workspace.md#remove-the-vminsights-solution-from-a-workspace). It's no longer needed.
121121

122122
> [!NOTE]
123123
> To check if you have any machines with both agents sending data to your Log Analytics workspace, run the following [log query](../logs/log-query-overview.md) in [Log Analytics](../logs/log-analytics-overview.md). This query will show the last heartbeat for each computer. If a computer has both agents, it will return two records, each with a different `category`. The Azure Monitor agent will have a `category` of *Azure Monitor Agent*. The Log Analytics agent will have a `category` of *Direct Agent*.

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,9 +72,9 @@ Heartbeat
7272

7373
If you don't see any data or if the computer hasn't sent a heartbeat recently, you might have problems with your agent. See the preceding section for agent troubleshooting information.
7474

75-
## Virtual machine doesn't appear in Map view
75+
## Virtual machine doesn't appear in the Map view
7676

77-
See the following sections for issues with Map view.
77+
See the following sections for issues with the **Map** view.
7878

7979
### Is the Dependency agent installed?
8080
Use the information in the preceding sections to determine if the Dependency agent is installed and working properly.
@@ -85,7 +85,7 @@ The [Log Analytics free tier](https://azure.microsoft.com/pricing/details/monito
8585
### Is your virtual machine sending log and performance data to Azure Monitor Logs?
8686
Use the log query in the [Performance view has no data](#performance-view-has-no-data) section to determine if data is being collected for the virtual machine. If no data is being collected, use the TestCloudConnectivity tool to determine if you have connectivity issues.
8787

88-
## Virtual machine appears in Map view but has missing data
88+
## Virtual machine appears in the Map view but has missing data
8989
If the virtual machine is in the **Map** view, the Dependency agent is installed and running, but the kernel driver didn't load, check the log file at the following locations:
9090

9191
| Operating system | Log |

0 commit comments

Comments
 (0)