Event Types

The Virtual Traffic Manager can respond to a wide variety of events, such as node failures, Traffic IP address transfers, Service Level failures and custom events raised from a rule. For convenience, individual events are grouped into a number of predefined types, and you can create new Event Types as required.

Event Type	Description
All Events	Includes all of the events that the Virtual Traffic Manager can detect; a built-in handler logs all events that match this type to the global Event Log.
Critical Problem Occurred	Includes all of the events that indicate a serious problem, including internal failures, node failures, IP transfers (because a Virtual Traffic Manager has failed) and other hardware problems.
Critical Problem is Resolved	Includes events that indicate that a problem that was raised in the “Critical Problem Occurred” Event Type has been resolved; for example, a failed node has started working again. If you configure the Virtual Traffic Manager to send an email message when a problem occurs, Ivanti recommends you also configure the Virtual Traffic Manager to send an email message if the problem is resolved and intervention is no longer necessary.
Default Events	Included for compatibility with earlier versions of the Virtual Traffic Manager. This event type includes all of the events that would cause the Virtual Traffic Manager to send an email message or raise an SNMP trap. When the Virtual Traffic Manager is upgraded from an earlier version, if necessary the upgrade process adds an Event Handler to preserve the earlier behavior.
Infrastructure Problem	These events are raised if the Virtual Traffic Manager detects a problem with an item of infrastructure; for example, if a server becomes un-contactable.
Service Problem	These events are raised if a problem is detected that could impact the successful delivery of a service.

To view the Event Types, click Manage Event Types.

Creating New Event Types

You cannot modify the built-in Event Types, but you can make a copy that can be edited, or you can create new Event Types from scratch.

For example, suppose that you use the Virtual Traffic Manager to manage several services, and you wish to create an Event Type that is matched when a particular service fails. You could then use that Event Type to create an event handler that emails the individual responsible for that particular service.

To do this, create a copy of the “Service Failed” Event Type, and edit the copy so that it is only matched when particular virtual servers, pools and nodes raise events. Perform the following steps:

Click Manage Event Types, and click the “Service Failed” Event Type.

You cannot modify this Event Type, but you can make a copy; Use the “Make a Copy of this Built-in Event Type” section to create a new Event Type called “Custom Service Failed”.

The Virtual Traffic Manager presents the Edit page for your new Event Type. Events are arranged in a tree structure; you can expand the nodes in the tree to see all of the events that the Virtual Traffic Manager can detect. The particular events that the Event Type matches are opened so that they can be easily seen.

Edit the new Event Type. You can change the list of health monitors, nodes, pools, rules, virtual servers, and other objects that raise events so that the Event Type is only matched when the objects relating to your specific service raise events.

To apply your changes, click Update. Then create an appropriate Event Handler for the new “Custom Service Failed” Event Type.