With an action (up to 128 can be created), the user specifies how they will be notified when a relevant event occurs.The following notification types are supported:
Action Type |
Description |
Local Caching without Collector |
Supports Collector |
Forwards events as emails |
Yes |
Yes |
|
Stores events and all other data in a support SQL database |
Yes |
Yes |
|
Submits events via HTTP(S) |
Yes |
Yes |
|
Write events to a text file (plain, XHTML or CSV) |
No |
Yes |
|
Forward events via UDP/TCP Syslog |
Yes (TCP only) |
Yes |
|
Forwards events as SNMP traps |
No |
No |
|
Executes a process |
No |
Yes |
|
Controls a service |
No |
No |
|
Reboots or shuts down the computer |
No |
No |
|
Sends a network message |
No |
No |
|
Plays a .wav sound file |
No |
No |
|
Displays a desktop notification |
No |
No |
|
Forwards events via the Jabber protocol |
No |
No |
|
Prints events via a dot-matrix ASCII printer |
No |
No |
Local Caching without Collector
Whether or not an agent will cache event log data that could not be delivered to the specified service (e.g. email, web service, ..)
Supports Collector
Indicates whether an action can be relayed via the collector, enabled via the "Use Collector" check box. When enabled, data (e.g. events) is relayed via the collector. Local data is cached if the collector is temporarily unavailable.
