> #### Key terms and definitions

> This section highlights some important terms and concepts to help you immediately begin working with OpenEdge resource monitoring plans and rules. For more detailed information about this terminology, see the Resource Monitoring Guide.

> Fathom resource monitoring terms include:

> - Resource — A specific component of your configuration such as a WebSpeed broker, AppServer broker, or NameServer instance. Other Fathom resources include CPU, memory, system, network, and OpenEdge database.
> - Resource monitoring — Criteria set up to monitor a resource's performance. As necessary, you can adjust the criteria according to your specific performance expectations.
> - Monitor — As specifically addressed in this guide, the combination of an OpenEdge resource, schedules, and rules. You can monitor any of these OpenEdge server-related resources:
> - AppServer brokers.
> - AppServer broker log files.
> - AppServer server log files.
> - WebSpeed brokers.
> - WebSpeed broker log files.
> - WebSpeed agent log files.
> - NameServers.
> - NameServer log files.
> A schedule defines a block of time in Fathom (for example, weekdays), and a rule (for example, the ReregisteredBroker rule) determines how a resource's performance is judged. For example, the AgentMemoryUsageHigh rule determines when the memory usage of a WebSpeed agent process exceeds the specified threshold.

> - Rules — The resource monitoring component that Fathom checks to verify whether a resource complies with its performance criteria. Rule values, or settings, can be established using Fathom-supplied default values or user-defined values. Also, WebSpeed and AppServer brokers can optionally use calculated, resource-specific baseline rule values as determined by the Configuration Advisor.
> Rules are broken when a resource is not in compliance with the rule-based criteria that you set up; Fathom generates alerts in the management console to alert you to this fact.

> - Rule Set — A combination of rules.
> - Defaults and default values — Values that are predefined in Fathom in one location but can apply in another location. Resource monitoring plans contain several default values. Some of the more general, common defaults pertaining to resource monitors include default schedule, default alerts, and actions. These defaults help expedite the setup tasks associated with configuring a monitoring plan. Also, there are default values associated with a given resource type. These types of default values include polling intervals and rule sets. See the "Default polling and trend values" section for details.
> - Schedule — Defines the block of time when a set of monitoring rules is active for a resource. When you add a monitoring plan to a resource, you specify the schedule to indicate when the monitoring plan will be active. Fathom supports using, modifying, and copying predefined schedules to help you define schedules quickly. However, you can also create new schedules to suit your operating needs.
> - Alerts — Notifications that some specified activity has occurred regarding an actively monitored resource. Alerts can occur to indicate a real or potential problem exists, such as a rule violation, or that a typical or interesting activity regarding a resource has occurred.
> - Actions — Activities that are triggered in response to alerts. For example, you might specify that you receive an e-mail if a WebSpeed agent is trimmed.
> - Resource monitoring plan — A plan that defines a block of time during which a specific resource is to be monitored and identifies the rules that are to be checked during the specified time frame. All resources you create in Fathom must have one or more monitoring plans before Fathom can monitor the resource. Monitoring plans provide you with access to data that is immediately usable in indicating performance failures, giving you an opportunity to improve performance and report on trends gathered over a period of time specified by you.
> - Baseline value — As used in this guide, a number that serves as the base for calculating a set of possible threshold settings based on your system's past activity for a specific rule. The Configuration Advisor determines a baseline value as part of its data analysis process to calculate recommended rule threshold settings for specific WebSpeed and AppServer rules. See Chapter 7, "Calculating Rule Threshold Settings Using the Configuration Advisor."

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