> #### Commonly used terms

> Terms commonly used in Fathom resource monitoring include:

> - Resource.
> - Container.
> - Collection.
> - Monitor and schedule.
> - Rules, alerts, and actions.
> - Resource monitoring plan.
> - FathomTrendDatabase.

> ##### Resource

> A resource is a specific component of your configuration. A resource might be:

> - A database or database log file.
> - A system resource, such as CPU, memory, disk, or 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, NameServer, or WebSpeed Transaction Server.
> Note: Fathom Management supports monitoring and managing the WebSpeedŽ Transaction Server product. Throughout this guide, references to the WebSpeed Transaction Server and WebSpeed are used interchangeably.

> When you install Fathom Management, Fathom automatically creates resource monitors for your CPU resource and memory resource and assigns default values, which you can change. Fathom also creates monitors for resources registered with the AdminServer; these resources include databases, AppServers, NameServers, and WebSpeed Transaction Servers.

> ##### Container

> A container represents a named instance of an AdminServer that is either running Fathom or has been configured to be monitored by Fathom. There is typically a 1:1 relationship between the host name and container name unless there are multiple AdminServers running Fathom on the same host.

> ##### Collection

> A collection is a user-defined group of resources.

> You can create and use a collection to better organize and operate on resources. For example, you might create a collection, known as Collection A, that includes all resources on which a particular application depends. You might then create another collection, known as Collection B, that is also dependent on one of the resources in Collection A. If the resource common to both Collection A and Collection B fails, the failure is reflected in the status of both collections, enabling you to determine quickly the extent and the impact of the failure.

> An administrator can create a private or a shared collection. An operator can create a private collection and see, but not create, a shared collection.

> A collection can include any number of the following resources:

> - Monitored resources, such as CPU, disk, memory, and database.
> - Jobs.
> - Reports.
> - Other collections.

> ##### Monitor, schedule, rules, and rule sets

> A monitor in Fathom is defined as the combination of a resource, schedules, and rules. The schedule defines a block of monitoring time in Fathom, and the rules determine how a resource's performance is judged while it is being monitored. Each rule verifies whether a resource complies with its performance criteria. Rules are considered broken when a resource is not in compliance with the criteria that you set up. When you are working with database, log file, AppServer, NameServer, and WebSpeed monitors, you can also use rule sets when monitoring performance.

> When you monitor a resource, you set up criteria by which you can keep track of the resource's performance. As necessary, you can adjust the criteria (against which performance is measured) to meet your expectations. For example, you might want to monitor a database twenty-four hours per day, seven days a week, and receive notification if the database shuts down abnormally.

> ##### Alerts and actions

> A broken rule generates an alert, which notifies you that some criteria have been violated.

> Fathom Management allows you to set up actions that trigger automatically in response to alerts. For example, you can establish that the system administrator receive an e-mail if a database experiences an abnormal shutdown.

> ##### Resource monitoring plan

> A resource monitoring plan, also known more simply as a monitoring plan, defines a block of time in which a specific resource is monitored and identifies the rules to be checked during the defined time frame. Any resource that you create in Fathom must have one or more monitoring plans before Fathom can perform any monitoring.

> Fathom uses monitoring plans to determine when to monitor a resource and which rules and criteria to use when evaluating a resource's compliance within these defined parameters. By defining more than one monitoring plan, you can specify different criteria (rules) for different times. For example, you might evaluate the rules for a database resource every five minutes Monday through Friday and only every thirty minutes on weekends.

> ##### FathomTrendDatabase

> Fathom allows you to store trend data, which is the monitoring information Fathom collects, in either a local or remote FathomTrendDatabase. If you choose to send trend data to a local database (the default), you specify the trend database location and the port used to connect to that database. If you choose to use a remote database, you specify the hostname and Web server port of the remote Fathom Web server. The trend database must be locally configured at the remote location. All values you enter for either option are validated.

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