Each DBAmon task runs multiple monitoring iterations. During each iteration, it checks all metrics for all instances that are being monitored. If DBAmon detects an event where an identical event occured on the prior iteration, it will NOT perform duplicate notification. It will write a row to the event history data, but it will not notify. This is only true if the text of the event is identical to the text of the event that occured for the same instance on the prior iteration.

This page describes how the notification process works for each possible event severity:

Event Severity	Action Taken
Critical	Ticket - The Ticket Userexit is invoked. This can be Pager - The Pager Userexit is invoked. This can be configured to send a message (<= 240 characters) to an alphanumeric pager. Email - Send an EMail message to ID's configured via the Notify_List: DBC Parameter. HTML Log File - Contains detail event information
Warning	User-Customizable - The Warn_Msg Userexit is invoked. This can be customized to take whatever action is required at your installation. HTML Log File - Contains detail event information
Informational	HTML Log File - Contains detail event information
User	HTML Log File - Contains detail event information Email - EMail ID's configurable via DBAmon config file
Performance	HTML Log File - Contains detail event information
Security	HTML Log File - Contains detail event information

DBAmon.com
This Document: http://www.dbamon.com/misc/notify.shtml