Try OpenEdge Now
skip to main content
Resource Monitoring
Resource Monitoring with OpenEdge Management : Identifying OpenEdge Management resources you can monitor : Monitoring a resource

Monitoring a resource

You select the resource you want to monitor, and create its monitoring plan. The overall steps, which are covered in greater detail throughout this guide, are provided here.
Once you install OpenEdge Management and set the initial configuration options, you can configure OpenEdge Management to monitor certain remote resources as well as local ones.
You can monitor the following resources in OpenEdge Management:
*A database or database log file
*A system resource, such as CPU, memory, disk, or a file system
*A network resource, such as TCP or UDP port, Ping (ICMP), or HTTP communication
*A file resource, such as a log file or other file you identify for monitoring
*An OpenEdge server component, such as an AppServer, a NameServer, or a WebSpeed Transaction Server
To monitor a resource in OpenEdge Management:
1. Create a resource monitor (for a database, file, network component, OpenEdge server component, or system component).
2. Create a monitoring plan for the resource monitor. The monitoring plan defines all the criteria you want to use to assess the resource's performance.
The monitoring plan consists of the following parts:
*One or more schedules that identify the time frame you want to monitor.
*One or more rules that identify the performance standards you set for the resource. If a standard established by a rule is not met, the rule is considered broken and OpenEdge Management generates an alert to notify you of the performance issue.
*An action that occurs when OpenEdge Management generates an alert about a performance issue. The following table shows a list of the available actions.
Table 2. OpenEdge Management actions
In response to this action . . .
OpenEdge Management . . .
Default action
Contains the e-mail action.
Email action
Generates an e-mail to a recipient you identify, notifying the recipient about the alert.
Log action
Records details about the alert in a log file.
SNMP trap action
Sends notification of the alert to your SMNP management console.
Compound action
Executes an action that consists of one or more other actions. A created job, for example, is a compound action.