Skip to content

Commit 339c11d

Browse files
authored
Update agent-manage.md
1 parent 0d9d2be commit 339c11d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-monitor/agents/agent-manage.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,13 @@ ms.date: 04/06/2022
88
ms.reviewer: luki
99
---
1010

11-
# Managing and maintaining the Log Analytics agent for Windows and Linux
11+
# Manage and maintain the Log Analytics agent for Windows and Linux
1212

1313
After initial deployment of the Log Analytics Windows or Linux agent in Azure Monitor, you may need to reconfigure the agent, upgrade it, or remove it from the computer if it has reached the retirement stage in its lifecycle. You can easily manage these routine maintenance tasks manually or through automation, which reduces both operational error and expenses.
1414

1515
[!INCLUDE [Log Analytics agent deprecation](../../../includes/log-analytics-agent-deprecation.md)]
1616

17-
## Upgrading agent
17+
## Upgrade the agent
1818

1919
Upgrade to the latest release of the Log Analytics agent for Windows and Linux manually or automatically based on your deployment scenario and the environment the VM is running in:
2020

@@ -109,7 +109,7 @@ az vm extension set \
109109
```
110110
---
111111

112-
## Adding or removing a workspace
112+
## Add or remove a workspace
113113

114114
### Windows agent
115115
The steps in this section are necessary when you want to not only reconfigure the Windows agent to report to a different workspace or to remove a workspace from its configuration, but also when you want to configure the agent to report to more than one workspace (commonly referred to as multi-homing). Configuring the Windows agent to report to multiple workspaces can only be performed after initial setup of the agent and using the methods described below.

0 commit comments

Comments
 (0)