Starting Database Monitors

Database Monitors are started and stopped in two different ways: manually through the Admin Console, or from a Business Process task. The monitor must be deployed before activation can take place.

What happens to the database trigger when the monitor starts and stops? Each time a Database Monitor starts, a trigger is created on the target database; this same trigger will be removed from the database when the monitor is stopped from Clarify.

Manual Start/Stop

These steps takes place in Admin Console | Resource Monitors.

  1. Under the Resource Monitor Types section, select Database Monitor. All deployed monitors appear in the Resource Monitors section. Any monitor that has already been started has a green indicator, while red indicators show that a monitor is not started.
  2. From the Resource Monitor section, select the Monitor you wish to start and click Start ().
    When a Database Monitor is promoted (bundled and deployed) to a server, so too will any dependent objects. Always make sure these related objects exist and are complete before deploying the monitor. A good practice is to make your monitor one of the last objects you create.

    From a Business Process

    Database Monitors can be started and stopped when called with the ControlDatabaseMonitor Business Process task. Another task, GetDatabaseMonitorState can also be helpful to check whether your Monitors are started or stopped. A typical use case may be to use the "Get" task to check for state, and then the "Control" task to enable the Monitor if found to be disabled.