> #### Data analysis and recommended values overview

> The goal of the Configuration Advisor's data analysis process is to determine a set, or range, of meaningful threshold values for a specific rule as used by your resources based on several factors.

> ##### User-supplied criteria

> Figure 7–1 shows an example of the initial Configuration Advisor page. In this example, the resource is an AppServer broker, asbroker1.

> Figure 7–1: Configuration Advisor page example

> On the Configuration Advisor page, you specify these values:

> - A particular period of time, such as a week, in which data about a given rule is gathered and stored in the FathomTrendDatabase. Consider using the Fathom-supplied default values associated with a rule to establish this setting.
> - A time frame that defines a representative period in which a rule is generally active or being used; this time frame is the period against which you want to calculate your baseline value. To gather this data with a high degree of accuracy, you will want to select a period of time in which your resources are most active. Active means when your resources are engaged, performing read, write, and update activities to your system.
> It is recommended that you use the Fathom-supplied Configuration Advisor-related default values for a set period of time (for example, one week) to capture data to the FathomTrendDatabase for a rule. This initial step will provide you sufficient data with which to perform the comparison.

> Note: Your monitoring plan schedules are not necessarily the best choice for a time frame. A schedule defines a period of time in which rules are in effect; it does not necessarily focus on time periods in which your resource usage is highest. For example, you might use the 24x7 monitoring plan schedule to constantly monitor your system, but want to select Monday through Friday from 8 a.m. to 6 p.m. to calculate your baseline settings.

> - The rule or rules for which you want to determine recommended values.
> The Configuration Advisor reviews monitoring plans defined for a resource, looking for polled rules that can be calculated by the Configuration Advisor. If any of these rules are present, it displays them as preselected (as identified by a check mark). Deselect any rules for which you do not want recommended values to be calculated by removing the check mark next to the rule. When you deselect the check mark, the Configuration Advisor does not calculate the rule threshold setting for that rule.

> ##### The Configuration Advisor's data analysis process

> When you submit the completed Configuration Advisor page, the Configuration Advisor extracts individual rule-related data from the FathomTrendDatabase. Based on the availability of a minimum requirement of 32 valid data samples per rule to be calculated for the designated date range, the Configuration Advisor determines a baseline value.

> A valid data sample is a data sample that is determined to be not a null value (any whole number that is not zero). For example, the Rejected Request Percent High rule is determined when the quantity of rejected requests is divided by the quantity of received requests. The result must be a non-zero, whole number.

> This baseline value is used to calculate the recommended ranges. A data sample of 32 identifies a statistically meaningful representative portion of a rule's performance data as stored in the FathomTrendDatabase. This sampling provides sufficient data from which the Configuration Advisor can determine a baseline value and subsequently perform a successful analysis of each rule's data.

> ##### An individual rule's definition

> Based on the availability of the values and data, the Configuration Advisor generates a set of recommended values, or settings, for each rule processed. As necessary, the range of values is adjusted to ensure that the rules do not violate the minimum or maximum allowable values for the rule.

> ##### Calculated recommended threshold rules

> Once the calculation process is completed for each rule, the Configuration Advisor presents its results on the Configuration Advisor calculations page. Your initial criteria and each rule and the associated monitoring plans for which the rule applies, are displayed. Figure 7–2 shows the page that appears after you have submitted your initial Configuration Advisor page.

> Figure 7–2: Configuration Advisor recommend thresholds page

> The following time period was used for analysis section of this page summarizes the values defined on the initial Configuration Advisor page. These values are displayed here to remind you about the time period criteria you set.

> The Rule section contains all the rule-related calculated data. For each rule that is successfully processed, the range of recommended results appears in the Recommended Values drop-down list; each rule row also displays the current rule setting for each rule as defined for each individual monitoring plan. You can select a recommended rule threshold setting and existing monitoring plan, or plans, to which you want the range to apply.

> The recommended settings are expressed in a mathematical expression consistent with the rule threshold's unit of measure. Figure 7–2 shows that the unit of measure for Queued Request Percent High is percent queued and Rejected Request Pernt High is percent rejected. The unit of measure for Process CPU High is percent.

> Note: As you compare the existing and recommended values, you can elect to change none, some, or all values for a rule and each individual monitoring plan.

> Until you click Update Selected Rules, Fathom does not apply any of your selections.

> If the data analysis calculation for a rule was unsuccessful, the Configuration Advisor cannot define a range and an Insufficient data for analysis message displays in the Recommended Values drop-down list field. For example, if a data sample for the defined time period is not equal to or greater than 32, this message displays because there are not enough data samples available from which the Configuration Advisor can suggest a meaningful recommendation.

Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095