Actions
When an event handler is triggered, the Virtual Traffic Manager will invoke the actions configured for that handler.
The Virtual Traffic Manager contains three built-in actions: E-Mail, SNMP Trap, and Syslog. Note that on a new install of the Virtual Traffic Manager, the E-Mail and SNMP Trap actions are not completely configured (you must first edit them to specify the required settings). However, when the Virtual Traffic Manager is upgraded from an earlier version, these settings are preserved.
You may create additional actions of the following types:
Type | Description |
|---|---|
This action sends a report of the event(s) that triggered the handler to the email addresses configured in the action. You can create several E-Mail actions with different email addresses, and use this to configure the Virtual Traffic Manager to email different individuals for different Event Types. | |
Log to external file | Events are always logged to the global event log, but this action can be used to additionally log events to a named log file. The format used is the same as the format used in the global event log. This action is useful when creating a dedicated log of particular events. Virtual Traffic Manager appliance/cloud users: When using this facility on a virtual or cloud instance, you should ensure your file is kept within ZEUSHOME. When applying an upgrade, all user-created files and directories outside of ZEUSHOME are likely to be lost. |
Log to syslog | This action sends a message to the syslog daemon on the named server. This action can be used to send particular events to an external monitoring and management tool that can accept syslog messages. |
Program | This action runs a script or other program that you have uploaded to the Virtual Traffic Manager system using the Upload and Manage Programs button on the action’s Edit page. For an example program, refer to Calling a Program or Script. |
SNMP Notify/Trap | This action sends an SNMP Notify or Trap to the named SNMP receiver application on the host specified. Traps are defined in the Virtual Traffic Manager MIB, which you can download from the action’s Edit page. The Virtual Traffic Manager supports SNMP v1, v2c, and v3. The configurable settings for this action are dependent on the version you specify on the Edit Action page, and directly mirror the available settings on the System > SNMP page (SNMP command responder options). For more details, see Monitoring Performance Using SNMP. |
SOAP Callback | This action sends a SOAP message to the named server. For an example of a SOAP action and a server that handles it, see Sending a SOAP Message. |
On the Alerting page, click the Manage Actions link to edit actions and create new actions.
You can also apply the internal Action “Bypass event log” to prevent events being logged to the global event log.
Testing Actions
When you create or edit an action, you can invoke it immediately with a ‘test’ event. This is a useful way of testing the correct configuration and operation of your actions.