> #### Testing and documenting your potential solutions

> The administrator puts two plans in place to monitor this particular situation.

> ##### Adding new Fathom monitoring plans

> The administrator determines that he has a few additional setup options and controls he might consider implementing. Using Fathom, he:

> - Adds a monitoring plan and rule for the CPU on the asbroker process so that the system will alert him should processing not go according to expectations.
> - Adds a system level CPU monitor and associated rule also to alert him to unacceptable asbroker processing.

> ##### Gathering more data

> Even though the immediate crisis has been resolved, the administrator's primary goal is to try to prevent it from reoccurring. The following lists identifies other ways to explore whether the crisis was a one-time occurrence or a problem that will happen again. The administrator:

> - Looks at a larger historical time period in Fathom Management using reports. Report data might show other instances in which the process has gone runaway and what activities occurred to correct the problem.
> - Reviews what has changed on the system to determine if a recent change has caused the issue.
> - Checks the issues and answers available in the KnowledgeBase (KBase) section of the Knowledge Center available by accessing `http://www.progress.com`.
> - Documents the problem and his efforts to correct it so that the information will be available for future reference.

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