Try OpenEdge Now
skip to main content
Resource Monitoring
Setting up Resource Monitoring : Calculating meaningful thresholds with the Configuration Advisor : Using the Configuration Advisor with a disk, CPU, or file system resource
 

Using the Configuration Advisor with a disk, CPU, or file system resource

You can use the Configuration Advisor with the following resources: databases, disks, CPU, file systems, AppServers, NameServers, and WebSpeed Transaction Servers. For details about using the Configuration Advisor with the database or AppServer, NameServer, or WebSpeed Transaction Server, see OpenEdge Management: Database Management or OpenEdge Management: Servers, DataServers, Messengers, and Adapters.
The way in which you use the Configuration Advisor with a disk, CPU, or file system resource is similar because each resource has only one rule. For each rule, the Configuration Advisor calculates recommended values based on a particular formula, as listed in the following table.
Table 5. CPU, disk, and file system rules and formulas
Resource
Rule
Formula
CPU
CPU High
CPU_Usr + CPU_System + CPU_Wait
Disk
Disk busy
Dev_Pct_Busy
File system
Filesystem used
FileSys_UsedPct
In the case of the CPU rule CPU High, the Configuration Advisor looks at the sum of CPU_Usr, CPU_System, and CPU_Wait when calculating recommended values; for the disk resource, the Configuration Advisor looks just at the Dev_Pct_Busy value.
The following procedure describes the process of creating meaningful threshold settings for a disk resource. However, the steps also pertain to the CPU and file system resources.
To use the Configuration Advisor with a disk resource:
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 disk whose rule definitions you want to review or modify.
The Disk: <disk name> page appears.
3. Click Configuration Advisor.
The Configuration Advisor page for the disk appears.
4. In the Start Date and End Date fields, define a date range that OpenEdge Management will use to collect data from the OpenEdge Management Trend Database. (The default data range covers one week.)
5. Under Choose time period to analyze, identify the time frame that defines a period in which the rules are generally active, or being used. This time frame is the period against which you want OpenEdge Management to calculate your baseline activity. (The default time period is Monday through Friday, 9:00 AM to 5 PM.)
In the Select rules (for analysis) section, the Disk Busy rule, which is the only rule available for analysis for a disk resource, is preselected.
6. Click Submit. The Configuration Advisor begins to calculate the threshold settings, and one of the following occurs:
*If sufficient data exists for analysis, the Configuration Advisor displays the calculated result.
*You can now review the Configuration Advisor's recommendation and choose whether or not to update your threshold values. See Reviewing the recommended threshold settings for details.
*If insufficient data exists for analysis, a message appears (under Recommend Values) informing you that there is insufficient data for analysis. For example, you might have fewer than 32 data samples stored in the OpenEdge Management Trend Database. In this case, consider expanding the time between the start date and the end date to capture more data. Then rerun the Configuration Advisor.