MONITORING

Event handlers
An event handler defines the action that IBM® Lotus® Domino™ takes when a specific event occurs. You can define an event handler to do one or more of the following:
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.

For example, suppose you create an event handler that defines the criteria as a replication event with a severity level of Fatal. Then any replication event that matches that criteria is handled based on the event handler you created. Or, you can create an event handler for all events of any type that have a severity level of Fatal. An event handler is generated only if the specified task creates an event. And event handlers based on custom event generators are triggered only if the associated event generator creates the event.

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.

See also