Syslog Log Sources
LogRhythm currently provides configuration guides for more than 60 syslog log sources, but the SIEM supports many more.
Our goal is to provide a configuration guide for every device the SIEM supports. If your syslog log source is not included yet, rest assured that we are working on it.
Syslog log sources cannot be moved from a Windows agent to a Linux agent (or vice versa) via the Move Log Sources Between Agents feature. Instead, retire the existing syslog log source and reconfigure it using the other agent.
Recently Added Guides
Name | Date |
---|---|
March 26, 2025 | |
March 26, 2025 | |
February 12, 2025 | |
January 15, 2025 | |
January 15, 2025 | |
November 20, 2024 | |
November 20, 2024 | |
September 25, 2024 | |
September 11, 2024 | |
August 28, 2024 | |
August 14, 2024 | |
August 14, 2024 | |
August 14, 2024 | |
August 14, 2024 | |
August 14, 2024 | |
August 14, 2024 | |
August 14, 2024 | |
August 14, 2024 |
Deprecated Guides
Name | Date |
---|---|
Solera Connector | March 25, 2020 |
Configure LogRhythm to Collect Logs
Only Global Admins or Restricted Admins with elevated View and Manage privileges can take this action.
These instructions assume you have already completed all procedures described in the specific device configuration guide for the logs you want to collect.
In the Client Console on the main toolbar, click Deployment Manager.
Click the System Monitors tab.
Double-click the System Monitor Agent that collect the information.
The System Monitor Agent Properties dialog box appears.Click the Agent Settings tab.
Right-click anywhere in the Log Message Sources Collected by this Agent grid, and then click New.
Click the Basic Configuration tab.
For Log Message Source Type, select the name of the log as provided in the specific device configuration guide, and then click OK.
Complete any additional steps described in the specific device configuration guide, if applicable.
To save the configuration, click OK, and then click OK again.