Default database monitoring plans
- Last Updated: March 30, 2020
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
Default database monitoring plans
OpenEdge Management provides a default monitoring plan for each managed database. The following figure shows a sample default database monitoring plan.

Note that the name of the database resource is displayed preceded by the AdminServer name. In this example, the FathomTrendDatabase is contained by vm-lx64oepsitdrv2.
The default monitoring plan shown above consists of the values described in the following table.
| Field | Default value | Description |
|---|---|---|
| Name | Default Schedule Plan | Identifies the name of the system-defined 24/7 default schedule that is used when the plan is active. |
| Poll | 5 mins | Identifies the polling cycle set up for this database resource monitor. The polling cycle is the frequency at which the resource's rules are checked. |
| Alerts | Enabled | Indicates whether alerts are active and if they will be generated when the plan is active. |
| Trend | Enabled | Indicates whether the data monitored while this plan is active will be stored in the OpenEdge Management Trend Database. (This option is not initially set as a default value unless you chose it when you added the database to OpenEdge Management.) |
| Rule summary | Default DB RuleSet | Consists of two rules: Abnormal Shutdown and Agent Abnormal Shutdown. |
Note: OpenEdge Management prevents the assignment of schedules that
share overlapping time periods. For example, if you have a Default Schedule set up for a
resource monitor, you cannot set up an additional plan because the Default_Schedule is defined
for 7 days a week, 24 hours a day. In order to add other plans you must modify or remove the
Default_Schedule from the plan.