You do not have to set up monitoring plans and rules for your CPU resource. OpenEdge Management automatically provides a default resource named CPU when you initially start up OpenEdge Management. You cannot delete this OpenEdge Management-provided default resource, nor can you change its name. However, you can change the values in the CPU resource's monitoring plan definition and rule definition.
To review the default CPU resource monitoring plan:
1. Click Resources > Go to Resources in the OpenEdge Management console menu.
All resources managed by your console appear in the grid frame.
2. Filter or search for, and select the default CPU resource you whose monitoring plan you want to review.
The CPU details page appears.
3. To review the values set in the CPU's monitoring plan definition and rule definition, click the monitoring plan in the Name column. The monitoring plan appears.
The default monitoring plan definition consists of the following values:
Schedule — Identifies the system-defined 24/7 default schedule used when the plan is active. The default is Default_Schedule.
Polling Interval — Identifies the polling cycle, which is the frequency at which the resource's rules are checked. The default is 5 minutes.
Alerts Enabled — Indicates whether alerts are active and will be generated when the plan is active. The default is true.
Trend Performance Data — Indicates whether you want to store performance data in the OpenEdge Management Trend Database. The default is true.
Trend every — Indicates how often performance data is trended. The default is 1 poll(s).
The default monitoring plan's rule definition consists of the following values:
Alert if CPU usage exceeds — Identifies when OpenEdge Management issues an alert on CPU usage. The default is 80.0%.
OpenEdge Management monitors the percentage of CPU usage according to the value you enter in the Alert if CPU usage exceeds field within the rule definition. OpenEdge Management polls the CPU according to the Polling Interval value. This value reflects the percentage of time that a processor is busy executing a nonidle thread. You can view this percentage as the time spent doing useful work. You can also extrapolate the idle time based on this statistic.
This statistic is presented as an average percentage based on snapshots taken at the beginning and end times of the defined sample period. Expressing the value as an average reduces the possibility of false alerts for random spikes in usage. For example, if your CPU monitor has a polling interval of 15 minutes, the average CPU time is calculated over this period of time.
Alert Severity — Identifies the severity level at which OpenEdge Management triggers an alert. The default is Error.
Throw alert after — Identifies at which point OpenEdge Management triggers an alert. The default is 2 failed poll(s).
Throw additional alerts — Indicates if OpenEdge Management will throw additional alerts. Possible values are true or false.
On alert perform action — Identifies the action that OpenEdge Management takes when an alert is generated. The default is Default Action.
Clear alert after — Identifies the number of successful polls after which OpenEdge Management clears the alert. The default is 0 successful poll(s).
On clear perform action — Identifies a user-defined action or a compound action. For example, OpenEdge Management might run a job that was defined as an action. The default is None.
Schedule — Identifies the system-defined 24/7 default schedule used when the plan is active. The default is Default_Schedule.
