Skip to content

Commit 0a28dba

Browse files
committed
Incorp BWren feedback
1 parent 58eb55e commit 0a28dba

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

articles/sentinel/forward-syslog-monitor-agent.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -12,15 +12,17 @@ ms.custom: template-tutorial
1212

1313
# Tutorial: Forward syslog data to a Log Analytics workspace by using the Azure Monitor agent
1414

15-
In this tutorial, you'll configure a Linux virtual machine (VM) to forward syslog data to your workspace by using the Azure Monitor agent. Use these steps to collect data from Linux-based devices where you can't install an agent like a firewall network device.
15+
In this tutorial, you'll configure a Linux virtual machine (VM) to forward syslog data to your workspace by using the Azure Monitor agent. Configure your linux-based device to send data to a Linux VM. The Azure Monitor agent on the VM forwards the syslog data to the Log Analytics workspace.
16+
17+
Use these steps to collect data from Linux-based devices where you can't install an agent like a firewall network device. Then use the Log Analytics workspace in Microsoft Sentinel or Azure Monitor to monitor your device.
1618

1719
In this tutorial, you learn how to:
1820

1921
> [!div class="checklist"]
2022
> * Create a data collection rule
2123
> * Verify the Azure Monitor agent is running
2224
> * Enable log reception on port 514
23-
> * Verify event logs are forwarded to Microsoft Sentinel
25+
> * Verify syslog data is forwarded to your Log Analytics workspace
2426
2527
## Prerequisites
2628

@@ -29,7 +31,7 @@ To complete the steps in this tutorial, you must have the following resources an
2931
- Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
3032
- Azure account with the following roles to deploy the agent and create the data collection rules:
3133

32-
|Build-in Role |Scope |Reason |
34+
|Built-in Role |Scope |Reason |
3335
|---------|---------|---------|
3436
|- [Virtual Machine Contributor](/azure/role-based-access-control/built-in-roles)</br>- [Azure Connected Machine Resource Administrator](/azure/role-based-access-control/built-in-roles) | - Virtual machines</br>- Scale sets</br>- Arc-enabled servers | To deploy the agent |
3537
|Any role that includes the action Microsoft.Resources/deployments/* | - Subscription and/or</br>- Resource group and/or</br>- An existing data collection rule | To deploy ARM templates |
@@ -107,7 +109,7 @@ A data collection rule is an Azure resource that allows you to define the way d
107109

108110
If your VM doesn't have the Azure Monitor agent installed, the data collection rule deployment triggers the installation of the agent on the VM.
109111

110-
## Verify Azure Monitor agent is running
112+
## Verify the Azure Monitor agent is running
111113

112114
In Microsoft Sentinel or Azure Monitor, verify that the Azure Monitor agent is running on your VM.
113115

@@ -125,9 +127,9 @@ In Microsoft Sentinel or Azure Monitor, verify that the Azure Monitor agent is r
125127

126128
## Enable log reception on port 514
127129

128-
Verify that the VM that's collecting the log data allows reception on port 514 TCP or UDP depending on the syslog source. Then configure the build-in Linux syslog daemon on the VM to listen for syslog messages from your devices. After you complete those steps, configure your linux-based device to send logs to your VM.
130+
Verify that the VM that's collecting the log data allows reception on port 514 TCP or UDP depending on the syslog source. Then configure the built-in Linux syslog daemon on the VM to listen for syslog messages from your devices. After you complete those steps, configure your linux-based device to send logs to your VM.
129131

130-
The following two sections cover how to add an inbound port rule for an Azure VM and configure the build-in Linux syslog daemon.
132+
The following two sections cover how to add an inbound port rule for an Azure VM and configure the built-in Linux syslog daemon.
131133

132134
### Allow inbound syslog traffic on the VM
133135

@@ -160,9 +162,9 @@ sudo wget -O Forwarder_AMA_installer.py https://raw.githubusercontent.com/Azure/
160162

161163
This script can make changes for both rsyslog.d and syslog-ng.
162164

163-
## Verify event logs are forwarded to your Log Analytics workspace
165+
## Verify syslog data is forwarded to your Log Analytics workspace
164166

165-
After you configured your linux-based device to send logs to your VM, verify that the Azure Monitor agent is forwarding event log data to your workspace.
167+
After you configured your linux-based device to send logs to your VM, verify that the Azure Monitor agent is forwarding syslog data to your workspace.
166168

167169
1. In the Azure portal, search for and open **Microsoft Sentinel** or **Azure Monitor**.
168170
1. If you're using Microsoft Sentinel, select the appropriate workspace.

0 commit comments

Comments
 (0)