Knowledge Center > Tips

In order to prevent potential strain on your system's resources and eliminate false Alerts on startup, you can configure various actions to occur after the ipMonitor Service loads:

1. Delay Monitor Testing - Monitor testing will be delayed by the number of minutes you specify. Assuming that ipMonitor is monitoring Services on the host machine, this delay allows those Services to start after a reboot before ipMonitor begins to monitor them.
2. Load a Specific Number of Tests - If you've chosen to delay Monitor testing, only the specified number of Monitors will be loaded after the time delay. By controlling the number of Monitors that begin testing immediately, you may prevent potential strain on system resources.
3. Load Group Dependencies First - All Dependency Monitors will be loaded first in order to prevent false failures and Alerts. Otherwise, a Monitor could potentially report a failure because the Group's Dependency Monitors have not yet been loaded.

To configure staggered Monitor loading, proceed with the following:

1. Log in to the ipMonitor Administration interface.
2. Click the Settings menu option, then select Server Settings.
3. Configure the After the ipMonitor Service Loads section as follows:
   
         • Delay Before Loading the Engine: 2 minutes
   
         • While loading, limit the number of simultaneous tests: 100 tests
   
         • Place a checkmark in the Load all Monitors marked as Group Dependency first checkbox.

4. Click OK to save your settings.

For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:

< Back

Last Updated: April 17, 2006 | What did you think of this topic?