Event handlers

You can define an event handler to do one or more of the following:

• Log the event to a configured destination
• Notify you that the event occurred and specify the method of notification
• Forward the event to another program for additional processing
• Prevent the event from being logged to the server console or to a specified destination
• Run an agent
• Send console commands and scripts

The Monitoring Configuration database (EVENTS4.NSF) includes default event handlers for server tasks. However, to customize how events are handled, you may want to create a custom event handlers. You can enable or disable an event handler, so you can easily disable a default event handler and replace it with a custom one.

When you create an event handler, you specify the condition -- for example, when an event meets or exceeds a threshold or meets a specified severity level -- that triggers it. To specify event handler conditions, you define a set of criteria, specify a task, or select a custom event generator that triggers the event handler.

You can also create different handlers for different severities. For example, you may want to be notified immediately if an event has a severity level of Fatal or Failure and choose to write the information to the log file or to the Monitoring Results database (STATREP.NSF). Normal levels of events may not interest you, so you may want to create a log filter to prevent normal events and severity levels from being logged to the log file or the server console.