Edit a health monitor
- In the navigation bar, click .
- In theSystem Setupsection, clickGlobal System HealthorSystem Health, depending on which system contains the monitor you want to edit.The System Visibility Console screen opens, displaying all of the system monitors in the system.
- When you locate the monitor you want to edit, click its name.
- The monitor details screen opens, displaying the current state of the monitor along with its recent testing history.
- Click any or all of the sections on the screen to edit the fields within them.
- When you have finished editing the monitor details, clickSaveat the bottom of the screen.
Change the granularity of the time frame displayed in the history table by clicking
Change the block of time you are looking at by clicking and . If the granularity is set to Monthly, for example, click the Previous button to display the testing history for the previous month.
Change the name of the monitor, its location on the Visibility Console screen, and the time and frequency of the monitoring checks.
Change the setting that determines whether the monitor appears on the Organization Visibility Console and whether errors and warnings about the monitor appear on the System tab on the
Update the test configuration script that is used in the monitor.
How is the state of this Health Monitor determined?
Change the way the state of the monitor is determined by selecting the other option:
most recent resultor
What happens when this Health Monitor reaches a particular state?
Change the implications of any or all of the states, and configure different transaction actions for any or all of the states.
Special Case: Edit the IIS Longevity Health Monitor
If you have more than one application server, you need to modify the default settings for the IIS Longevity health monitor using the following values:
- WarningCountThreshold: Default value: 2. This default assumes one application server. For a multiple application server installation, change the value ofWarningCountThresholdto (application server count) x (default). For example, if there are two application servers, the value should be 4.
- ErrorCountThreshold: Default value: 5. The default setting assumes one application server. For a multiple application server installation, change the value ofErrorCountThresholdto (application server count) x (default). For example, if there are two application servers, the value should be 10.