═══ 1. Help For Application Monitor ═══ Application Monitor General Help The C.O.L. Systems Inc. Application Monitor (AppMon) is one of the Pegasus Tools utilities. With AppMon you can monitor one or more instances of a specific application, as well as children processes that the main application spawns. With AppMon you can monitor each Thread and/or File that the application(s) reference. You can also monitor the system CPU during collection. AppMon collects all measurements and stores them to a log file of your naming choice. This log file can then be processed by PegLog, the post processing log utility. ═══ 2. Help For Application Monitor Main Window ═══ Application Monitor Main Window Monitoring an application is now a simple process: 1. Enter the name of the process that you want to monitor, making sure to include the 'EXE' or 'COM' extension. 2. Setup a log file to collect measurements to. If the 'Use Log File' check is not set, logging will be disabled. 3. Set whether you want to collect measurements for single or multiple instances of the named process, as well as any children it may spawn. 4. Set which measurement you want to collect. 5. Optionally, change the default frequency and duration for the monitor session. 6. Click Start! 7. When complete, run PegLog against the log to produce output in report or table format. For detailed help on each of the options in this screen, click on the option then press the F1 key. ═══ 2.1. Help For Application Name ═══ Application Name This is where you identify the process name that you want to monitor. You must supply the name for the process that usually appears in the rm2stat list: For example: EPM ===> enter EPM.EXE This is a required field. ═══ 2.2. Help For Frequency Minutes ═══ Frequency Minutes Set the number of minutes between samples for the monitored application. Valid minutes range is 0-59. ═══ 2.3. Help For Frequency Seconds ═══ Frequency Seconds Set the number of seconds between samples for the monitored application. Valid seconds range is 0-59. ═══ 2.4. Help For Duration Hours ═══ Duration Hours Set the number of hours that the monitored application should collect data for. Valid hours range is 0-23. Pegasus Application Monitor allows you to set a watchdog timer that, when elapsed time is completed, will stop monitoring the selected application. This timer will be relinquished if the application ends before it expires. ═══ 2.5. Help For Duration Minutes ═══ Duration Minutes Set the number of minutes that the monitored application should collect data for. Valid range is from 1-59. Pegasus Application Monitor allows you to set a watchdog timer that, when elapsed time is completed, will stop monitoring the selected application. This timer will be relinquished if the application ends before it expires. ═══ 2.6. Help For Single Application Tracking ═══ Single Application This option indicates wheter Pegasus Application Monitor should monitor only a single instance of an application with the same name. If not set, all applications with a matching name will be monitored. ═══ 2.7. Help For Children Tracking ═══ Children Tracking This option indicates whether children processes of the monitored application are to be monitored as well. If not set, Pegasus Application Monitor will discard children process statistics. ═══ 2.8. Help For Thread Tracking ═══ Thread Tracking For each application, every thread can be monitored. This option indicates that Pegasus Application Monitor should collect thread activity for the process being monitored. Note: You must select either Thread, File or both for application monitoring. ═══ 2.9. Help For File Tracking ═══ File Tracking For each application, every file that is accessed by the process can be tracked. This option indicates that Pegasus Application Monitor should collect file activity for the process being monitored. Note: You must select either Thread, File or both for application monitoring. ═══ 2.10. Help For System CPU ═══ System CPU In addition to tracking application thread percent busy, the overall System percent busy can be collected. With this option, System CPU statistics will be written to the log (if activated) as well as displayed in the CPU % indicator during monitoring. ═══ 2.11. Help For End Of Run Default ═══ End Of Run Default This button controls what action to take when an end of process run is detected. The default is based on the following rules: 1. Single Instance with Children - AppMon will wait until any running children processes have ended as well. It will then close the log. 2. Single Instance with No Children - AppMon will close the log. 3. Multiple Instance with Children - AppMon will wait until all instances and children have ended before closeing the log. 4. Multiple Instance with No Children - AppMon will wait until all instances have ended before closeing the log. Note: If you have duration set and it expires before any of the above rules take effect, AppMon will close the log. ═══ 2.12. Help For End Of Run Auto Close ═══ End Of Run Auto Close This button controls what action to take when an end of process run is detected. The Auto Close is based on the following rules: 1. Single Instance with Children - AppMon will close the log when the parent process has ended. 2. Single Instance with No Children - AppMon will close the log. 3. Multiple Instance with Children - AppMon will wait until all parent instances have ended before closeing the log. 4. Multiple Instance with No Children - AppMon will wait until all instances have ended before closeing the log. Note: If you have duration set and it expires before any of the above rules take effect, AppMon will close the log. ═══ 2.13. Help For End Of Run Prompt ═══ End Of Run Prompt This button controls what action to take when an end of process run is detected. The user will be prompted to close the log or continue based on the following rules: 1. Single Instance with Children - AppMon will wait the parent ends and then prompt to continue monitoring children if there are children running, otherwise it will close the log. 2. Single Instance with No Children - AppMon will close the log. 3. Multiple Instance with Children - AppMon will wait until the parent ends and the prompt to continue monitoring multiple instances if there are multiple instances running, otherwise it will close the log. 4. Multiple Instance with No Children - AppMon will wait until the parent ends and the prompt to continue monitoring multiple instances if there are multiple instances running, otherwise it will close the log. Note: If you have duration set and it expires before any of the above rules take effect, AppMon will close the log. ═══ 2.14. Help For Application Monitor Start ═══ Application Monitor Start This button, when clicked, will start the application monitor if settings fields are properly set. Once the application has started being monitored, the Stop button will be available to cancel the operation. ═══ 2.15. Help For Application List ═══ Application List Once the application monitor begins, this list box will fill with the fully qualified name of the applications found to monitor. ═══ 2.16. Help For File List ═══ File List Once the application monitor begins, this list box will fill with the fully qualified name of the files opened for the applications being monitored. Note: This box will only be filled if: o The File Tracking option is set. o The monitored application opens files. ═══ 2.17. Help For CPU Activity ═══ CPU Activity This gauge control displays the total system CPU percent busy. Note: This is only active if the System Cpu option is set. ═══ 2.18. Help For Use Log File ═══ Use Log File If this option is set (checked), then the log file you have identified using the Set Log option will be used to collect data measurements to. ═══ 2.19. Help For Set Log ═══ Set Log Use this control to setup the name of the log file where you want to collect measurements to.