Syslog is an early remote logging option that, even today, provides us with yet more options with regards to multi-platform functionality in mixing Windows and *nix for logging various bits of information.

There are many documents available on the Internet providing information and details regarding the use of syslogd and the possible uses are beyond the scope of this document.

In this example, we have configured our syslogd to accept messages from our ipSentry machine and configured various actions on the Unix box based on the type and content of these messages.  The task at hand is to get the message to the syslogd when a monitored item fails or recovers. We will be sending a user message with alert priority.

1. While editing an entry...
    

2. Select the Syslog tab under Alerts tab.
    

3. Set the Alert Status option to Enabled
    

4. Mark the Alert Success option as Checked.
    

5. Enter the IP Address of the machine running syslogd.
    

6. Set the port to 514 (standard Syslog port)
    

7. Select user in the Facility list.
    

8. Select alert in the Priority list.
    

9. Enter the message that should be sent.
   Again, ipSentry keywords are available in this text.
    

10. Set the Alert Schedule as desired.
     

11. Hit OK to save the changes.

Now, when the item fails, an alert will be send to our Syslog daemon as a USER:ALERT containing the message text defined in the configuration, upon which, various processes may act based on configuration of the remote system, syslogd, cron, and etc.