Adding and editing a Syslog Action

When a device does not respond to polling, you can send a Syslog message to a host that is running a Syslog server.

To add a new Syslog action:

1. From the WhatsUp Gold web interface, go to Admin > Actions. The Action Library appears.
2. Click New. The Select Action Type dialog appears.
3. Select Syslog Action, then click OK. The New Syslog Action dialog appears.
4. Enter or select the appropriate information:
   • Name. Enter a unique name for the action. This name displays in the Action Library.
   • Description. (Optional) Enter additional information about the action. This description displays next to the action in the Action Library.
   • Syslog Server. Enter the IP address or hostname of the machine that is running the Syslog server.
   • Port. Enter the UDP port that the Syslog listener is listening on. The default port is 514.
   • Message. Enter a text message to send to the Syslog server. This message may include notification variables. The Syslog message box limits input to 511 characters. If notification variables are used, then the message that actually gets sent is limited to 1023 bytes, in order to comply with the Syslog protocol. Non-visible ASCII characters such as tabs and line feeds are replaced by space characters.
5. Click OK to save changes.

Note: If you attempt to run another application on the same system that also listens on the same Syslog port as WhatsUp Gold, the error message Unable to Open Socket displays.

Note: The WhatsUp Gold Syslog listener runs on Port 514 by default. This port can be configured in the WhatsUp Gold console at Configure > Program Options > Passive Monitor Listeners > Syslog.

Tip: To check the status of an action, or to cancel an action, in the WhatsUp Gold console go to Tools > Running Actions.

To edit an existing Syslog action:

1. From the WhatsUp Gold web interface, go to Admin > Actions. The Action Library dialog appears.
2. Select the action you would like to edit, then click Edit.
3. Enter or select the appropriate information:
   • Name. Enter a unique name for the action. This name displays in the Action Library.
   • Description. (Optional) Enter additional information about the action. This description displays next to the action in the Action Library.
   • Syslog Server. Enter the IP address or hostname of the machine that is running the Syslog server.
   • Port. Enter the UDP port that the Syslog listener is listening on. The default port is 514.
   • Message. Enter a text message to send to the Syslog server. This message may include notification variables. The Syslog message box limits input to 511 characters. If notification variables are used, then the message that actually gets sent is limited to 1023 bytes, in order to comply with the Syslog protocol. Non-visible ASCII characters such as tabs and line feeds are replaced by space characters.
4. Click OK to save changes.

Note: If you attempt to run another application on the same system that also listens on the same Syslog port as WhatsUp Gold, the error message Unable to Open Socket displays.

Note: The WhatsUp Gold Syslog listener runs on Port 514 by default. This port can be configured in the WhatsUp Gold console at Configure > Program Options > Passive Monitor Listeners > Syslog.

Tip: To check the status of an action, or to cancel an action, in the WhatsUp Gold console go to Tools > Running Actions.

See Also Configuring an action Adding and editing an Active Script Action Adding and editing a Beeper Action Adding and editing an Email Action Adding and editing a Log to Text File Action Adding and editing a Pager Action Adding and editing a PowerShell action Example - PowerShell action scripts Adding and editing a Program Action Adding and editing a Service Restart Action Adding and editing a SMS Action Adding and editing a SMS Direct Action Adding and editing a SNMP Set Action Adding and editing a Sound Action Adding and editing a SSH Action Adding and editing a Text-To-Speech Action Adding and Editing a VMware Action Adding and Editing a Web Alarm Action Adding and Editing a Windows Event Log Action Using the WinPopup Action