Skip to main content
Skip table of contents

Configure Secure Syslog to System Monitor Agent

Windows System Monitor


  1. IP or Hostname of a Microsoft Windows machine with system monitor installed and secure syslog configured on the LogRhythm System Monitor.
  2. A valid certificate to create the secure channel.
  3. Encrypt and configure a secure syslog agent to be sent to a system monitor agent. For more information, see Configure a Secure Syslog Agent.


You can configure the Open Collector to send data to a System Monitor configured with secure syslog using the following steps:

  1. Run Command

    ./lrctl oc config edit
  2. Enter the hostname or IP of your Windows System Monitor agent with secure syslog configured.
  3. Enter port where system monitor is listening to receive data on secure connection. By default System Monitor is configured to listen on port 6514 for secure syslog.
  4. Select the Time Zone.
  5. When asked to change System Monitor sending mode, type 'y'.
  6. You will be shown option to change Transport Mechanism, select 'TLS' .
  7. For "Beats listener mode" option, type 'N'
  8. For option to change "advance properties", type 'N'
  9. Then you will be asked to change cert content, type 'y'. This is asked since you selected transport mode TLS to send syslog to System Monitor.
  10. Copy and paste certificate content as shown below with "Begin Certificate" and "End Certificate" tags included and hit enter twice when finished.
  11. The configuration will be saved
  12. For the changes to take effect, run command

    ./lrctl oc restart

Linux System Monitor

Linux System Monitors do not support secure syslogs as of the current release.  However, they can collect normal syslog data from System Monitor version onwards.

For more information on installing a System Monitor on UNIX/Linux, see Install a System Monitor on UNIX/Linux.

Installing the SysMon agent on the same machine as the Open Collector is not supported. Collection is supported from another machine running Linux.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.