> #### Getting started with log files for WebSpeed resources

> For each local WebSpeed broker that Fathom Management discovers, Fathom supports monitoring its two associated log file monitors. Fathom provides a log file resource monitor for the WebSpeed broker itself and another for its associated agents. Each of these log file monitors has its own log file monitoring capabilities.

> WebSpeed log file resource monitors are not enabled until the WebSpeed broker for which the resource monitors were created is started. When the log file monitor first starts monitoring either a WebSpeed broker or agents, it always starts at the end of the log file.

> ##### Naming conventions

> Fathom prepends the broker's name to the name of the broker and agent log file monitors and viewers. For example, Fathom generates the following log file monitor and associated viewer names for a WebSpeed broker instance named wsbroker1 and the container named vesta:

> - Broker-related log file names — Displays vesta.wsbroker1BrokerLogFileMonitor and vesta.wsbroker1 Broker Log File Contents.
> - Agent-related log file names — Displays vesta.wsbroker1AgentLogFileMonitor and vesta.wsbroker1 AgentLog File Contents.

> You cannot change these names.

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