Database Management Technology 
The Alarm Editor is used to manage Sentinel alarm configurations on remote nodes. A Sentinel configuration consists of a unique Sentinel name, a collection of alarm conditions, and an execution schedule. You can create multiple Sentinel configurations, such as workday, evening, and weekend and assign the appropriate execution schedule to each. The Sentinels will then start and shut down automatically according to the defined execution schedule.
The example above defines an alarm named SESSION_LOCK_WAIT which will detect database server threads waiting for lock requests to be granted. The alarm condition will be checked every 30 seconds. Column values can be embedded in the message text by preceding the column name with a : (colon character).
The Detail tab defines the query to execute as well as the alarm severity conditions. In the example above sessions waiting over 60 seconds will generate critical alarms.
