Version 4.1 User's Guide
Troubleshooting Using The Activity Monitor	Previous Contents

Eventually, the need to troubleshoot some PageSentry operations is inevitable. Whether a Sentry test is not completing as you expect, a Notifier doesn't perform it's action, or Web reports fail to work, the best way to see exactly what is happening within PageSentry is through the Activity Monitor.

The Activity Monitor is opened by choosing "Open Activity Monitor" from the "File" menu. Once open, it simply displays a running log of activity, as it occurs within PageSentry. The activity can also be stored to a text file called "PageSentry Activity Report". The detail of the messages stored in the Activity Report or displayed in the Activity Monitor can be set using the pop-up menus at the bottom of the window.

Debug

When the Display Level (or Report Level) is set to "Debug" every detail of PageSentry operation is displayed or logged. This level of detail is almost never required, and this option is not recommended during normal use.

Verbose

The Verbose level causes a very fine level of detail to be included in the log file or display window. For example, the text sent between PageSentry and the server during testing will be shown, as will all normal status messages, warnings, and errors. This mode will generate a great deal of text, which may bog down PageSentry and cause the Activity Log to grow quickly. It is therefore best used only temporarily during debugging.

Basic

In Basic mode, Sentries and Notifiers will report their status after significant actions (such as performing a test or executing a notification), but won't display details as the actions take place. Warnings and errors will also be displayed if/when they occur.

Warnings

The Warning level will report unexpected events while skipping over regular occurances. Sentry tests that fail, for example, will be reported, but successful tests will not.

Errors

Only errors that effect PageSentry's ability to perform it's job will be reported. Errors detected by PageSentry on remote servers are part of PageSentry's normal operation, and will therefore not be displayed when the Display Level is set to Error. Low memory situations, networking problems, and other internal errors will cause messages to be displayed or logged.

Suspend

No messages will be logged or displayed at all. This is useful for freezing the display to look carefully at a series of lines, or to turn off the Activity Log altogether.

Perhaps the best example of how the Activity Monitor can be of help is in creating a Telnet Notifier. Telnet Notifiers run a script which sends a series of commands to a Telnet device, such as an APC Masterswitch. In this case, the Activity Monitor acts as a window into the Telnet session between PageSentry and the Masterswitch.

First, open the Activity Monitor and set the level to "Verbose". You may also want to take all Sentries "Off Duty" or open the Snooze window so that extraneous messages aren't displayed while you are reviewing the Telnet script. Then open the Telnet Notifier window and click "Run It". As the script executes, the entire transcript of the session will be displayed. If your script makes a wrong menu selection or issues an incorrect command, you should be able to recognize the problem quickly, and make the needed correction.

This same technique can be used for most Sentries and Notifiers. For example, Web Sentries will show the HTTP request and response headers, FTP Sentries will display the login transaction, etc. Even if you don't have a firm understanding of how these protocols work, seeing how PageSentry interacts with your servers is helpful in resolving just about any problem.

Copyright © 1995-2002 Maxum Development Corporation http://www.maxum.com/ Rev. 7/10/02	Previous Contents