v1.7 iis AC Configuration

The IIS Server Monitoring (iis) probe monitors the health and status of Microsoft IIS servers. The probe performs HTTP GET queries to the selected Microsoft IIS servers. The probe uses the query result for generating alarms and QoS.
uimpga-ga
iis_1.7_AC
The IIS Server Monitoring (iis) probe monitors the health and status of Microsoft IIS servers. The probe performs HTTP GET queries to the selected Microsoft IIS servers. The probe uses the query result for generating alarms and QoS.
The following diagram outlines the process to configure the probe to collect QoS data for Microsoft IIS servers.
 
Configuring IIS
Configuring IIS
Contents
Verify Prerequisites
Verify that required hardware and software is available before you configure the probe. For more information, see iis (IIS Server Monitoring) Release Notes.
Add Host
You can add the IIS host server under the 
iis
 node to monitor the IIS server.
Follow these steps:
  1. Click the 
    Options (icon)
    next to the 
    iis
     node in the navigation pane.
  2. Click the 
    Add New Host
     option.
  3. Set or modify the following values in the 
    Add New Host
     window
    • Hostname or IP Address: Enter the name or IP address of the IIS server to be monitored.
    • Active: Enables you to activate the host for monitoring.
      Default: Selected
    • Alarm Message: Specify the alarm message to be used when the host does not respond.
      Default: MsgAgentError
    • URL for http response: Specify the address to be tested for http response. For example, http://10.112.69.14 or http://www.msn.com.
    • Description: Specify a short description of the monitored host.
    • Data Collection Interval (min): Specify how often the probe collects data from the host.
      Default: 1
    • Filter Port: Define the port which is used to communicate between the IIS add-on (IISrequest.dll) and the probe. This option is used for monitoring the IIS server remotely.
      Default: 999
    • Windows Username: Define a valid user name with administrator privileges for logging in to the monitored host.
    • Windows Password: Define the password for logging in to the monitored host.
    • Windows Domain: Define the DNS domain name for locating the IIS server when it is not hosted on the local system. Leave the field blank, when both IIS and probe are installed on the same system.
    • Http Server Authentication: Specify the auhentication type as follows:
      • None: indicates no authentication against the http server (still requires the Windows authentication for performance data).
      • Basic: indicates basic authentication against the http server. The 
        Http Username
         and 
        Http Password
         fields values are used for the authentication.
      • Windows: uses the Windows authentication credentials as specified in 
        Windows Username
         and 
        Windows Password
         fields.
The probe does not support HTTP Response value monitor for HTTPS connections.
    • Http Username: Define a valid user name with administrator privileges of the http server.
    • Http Password: Define the password for logging in to the http server.
  1. Click
    Submit
    .
  2. Click the 
    Test Windows Credential
     option from the 
    Actions
     drop-down to verify the entered values.
    The host is saved under the 
    iis
     node. Every new host contains four child nodes (
    ASP
    IIS
    System
    , and 
    Webservices
    ), which are used to configure the monitoring properties of the host.
uimpga-ga
Alarm Thresholds
The alarm threshold options that are available can vary depending on the probe versions installed at the hub level. The alarm threshold settings to allow the probe to:
  • Send alarms when threshold criteria is met
  • Indicate to baseline_engine to compute baselines
See Configuring Alarm Thresholds for details.
Monitor the Application Pool
Monitoring the health and status of the application pool is important for the website administrator. This monitoring ensures web site availability and response time at an optimum level. The probe gives the lists of available application pools on the monitored host and lets you configure monitoring counters for each application pool separately.
The Application Pool monitoring feature is applicable for IIS 7.0 or later. The APP_POOL_WAS counter must be available on the Windows Performance Monitor of the system where IIS 7.0 server or later is installed.
Follow these steps:
  1. Go to the
    Application Pool
    node in the navigation pane.
  2. Select more than one application pool from the
    Available
    list and move to the
    Selected
    list and click
    Save
    .
    The selected applications pools appear under the
    Application Pool
    node in the navigation pane.
  3. Select the appropriate
    application pool name
    node.
  4. Activate the application pool monitoring in the
    General Configuration
    section.
  5. Activate the required monitoring counters of the application pool.
  6. Click
    Save
    .
    The probe starts fetching values for the selected monitoring counters of the application pool for generating alarms and QoS.
Set Device ID Key Using Raw Configure
If you want to monitor local Microsoft IIS servers, and you also want to create the probe Device ID same as robot Device ID, set the
useRobotDevIDForLocalhost
 key to
Yes
. By default, this key is set to
No
.
Follow these steps to change the Device ID key value
:
  1. Open the Raw Configuration interface of the probe.
  2. Click the
    Setup
     folder.
  3. Click the default value 
    no 
    and change the value to 
    yes. 
  4. Click 
    Apply
    The iis probe now monitors local IIS servers.
There may be the following impact of setting this key: 
Probe Version
Key Value
Impact
Previous to v1.71
NA
NA
Upgrade to v1.71
No
No Impact
Upgrade to v1.71
Yes
Previously, all QoS and alarms for the local host profile were generated on the old Device ID. Now, the probe generates all the QoS and alarms for local host profiles on the new Device ID i.e. Robot Device ID. This breaks the old data continuity on the USM portal.