iis AC Configuration

This article is for probe version 1.8 or later.
This article describes the configuration concepts and procedures to set up the IIS Server Monitoring (iis) probe. The probe generates HTTP GET queries to the specified Microsoft IIS servers and uses the response to generate alarms and QoS. You can create host profiles that include the predefined counters to monitor the IIS server performance.
This article is for probe version 1.8 or later.
The following diagram outlines the process to configure the probe.
Configuring IIS
Configuring IIS
Verify Prerequisites
Verify that required hardware and software is available and any installation consideration is met before you configure the probe. For more information, see iis (IIS Server Monitoring) Release Notes.
Configure General Properties
The probe is deployed with default values as part of recommended configuration. You can change the default configuration of the probe if they do not meet your needs. For example, you can specify the log level, maximum data storage time, and number of profiles that are run simultaneously. 
Follow these steps:
  1. Click the 
    Options  (icon)
     next to the 
     node in the navigation pane.
  2. The 
    specifies the level of details that are written to the log file. You can select the following log levels:
    • 0 - Logs only severe information (default)
    • 1 - Logs error information
    • 2 - Logs warning information
    • 3 - Logs general information
    • 4 - Logs debugging information
    • 5 - Logs tracing/low-level debugging information
    Log as little as possible during normal operation to minimize disk consumption, and increase the amount of detail when debugging.
    (From version 1.91)
    Log Size (KB):
     specifies the maximum size of the probe log file, in kilobytes. When this size is reached, new log file entries are added and the older entries are deleted.
    Default: 100 KB
  4. To configure the advanced details of the probe, complete the following field details:
    • Max Summary Storage
      : specifies the maximum data storage time for local monitoring. This value is the time range within which the monitored values are picked to calculate the average value (used when setting the alarm threshold). This option does not affect the QoS data.
      Default: 6 hours
    • Maximum Concurrent Threads
      : specifies the maximum number of profiles the probe can run simultaneously. You can run up to 100 profiles simultaneously.
      Default: 20
Create Host Profile
You can create profiles in the probe to monitor the IIS server. Each profile uses a connection to an IIS server to collect and store monitoring data.
Follow these steps:
  1. Click the 
    Options  (icon)
     next to the 
     node in the navigation pane.
  2. Click the 
    Add New Host
  3. Specify the following field values in the 
    Add New Host
    • Hostname or IP Address
      : specifies the host name or IP address of the IIS server to be monitored.
    • Active
      : allows the profile to start monitoring the IIS server, on creation.
      Default: Selected
    • Alarm Message
      : specifies the alarm message that is generated when the host does not respond.
      Default: MsgAgentError
    • (Optional) URL for http(s) response
      : specifies the address to be tested for http or https response. For example, http://www.msn.com.
    • Description
      : specifies additional information about the profile.
    • Data Collection Interval (min)
      : specifies how often the probe collects data from the host.
      Default: 1
      Reduce this interval to generate alarms and QoS frequently. A shorter interval can also increase the system load.
    • Filter Port
      : specifies the port number that the probe uses to communicate with the IIS add-on (IISrequest.dll). Specify the same port number in the probe and the IIS server to ensure connectivity. This option is used to monitor the IIS server remotely.
      Default: 999
    • Windows Username
      : specifies a valid Windows username with administrative privileges to connect to the host.
    • Windows Password
      : specifies the password of the defined 
      Windows Username
    • Windows Domain
      : specifies the DNS domain name for locating the IIS server when it is not hosted on the local system.
      You must leave this field blank when both IIS and probe are installed on the same system.
      Http(s) Server Authentication
      : allows you to select one of the authentication types as follows:
      • None
        : indicates no authentication against the http server (still requires the Windows authentication for performance data).
      • Basic
        : indicates basic authentication to access the http server. Specify the required user credentials in the
         Http(s) Username
        Http(s) Password
      • Windows
        : uses the Windows authentication credentials. 
        Http(s) Username
        : specifies a valid user name with administrator privileges to connect to the HTTP(S) server.
        Http(s) Password
        : specifies a password for the given username.
  4. Click 
    The host is created under the 
     node and contains five child nodes (
     Application Pool
    ) that are used to configure the monitoring properties of the host.
     If you want to use Https server authentication, navigate to the
     Host name 
    > IIS Server
     node, and under the 
    SSL Setting
     section, update the following field information:
    • Use SSL:
       allows you to use
      the SSL certificate verification.
      Default: Not selected
    • Peer Verification:
       allows the probe to enable peer verification. Peer is the certification authority that issues SSL certificates.
    • Certificate Authority Bundle Path:
       specifies the certification bundle path for SSL verification. The bundle contains certificates of all the issuing authorities and can be obtained from 
      to add a certificate to the bundle, see https://www.watchguard.com/help/docs/ssl/2/en-US/Content/FAQs/add_bundled_certificates_faq.html. The SSL certificate bundle path should point to a file that has one or more certificates to verify the peer.
      Host Verification:
       allows the probe to enable host verification for validating the SSL connection.
      Host Verification Level:
       select one of the following two levels of host verification:
        : defines the level where the host name that is entered in the Server address field is not verified against the Common Name (CN) attribute appearing in the SSL certificate. The verification checks if the IP address/host name points to the same server.
      • Strict
        : defines the level where the host name that is entered in the Server address field is verified against the CN attribute appearing in the SSL certificate. If the host name does not match with the CN field, the session request gets rejected.
      (From version 1.90) 
      When you enable 
      Host Verification
      , a new counter, 
      SSL Host Verification Status
      , is added to the counters list for the host. You can configure this counter to monitor the verification state and generate alarms when the host verification fails.
  6. Click the 
    Test Windows Credential
     option from the 
     drop-down to verify the entered values.
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
An application pool allows you to run websites or URL in groups. Each group is part of the different application pool. Each application pool runs in a different worker process of the IIS server and each worker process runs in isolation. This isolation prevents other application pools from going down when one application pool is down. You can also define different security rights for each application pool.
You can monitor multiple application pools of the IIS server, and configure multiple counters of each application pool for monitoring. This monitoring ensures the website availability and response time at an expected level.
 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. Click the 
    Options (icon)
     next to 
  3. Select the required application pool from the 
     list to move to the 
     list and click 
    The selected applications pools appear under the 
    Application Pool
     node in the navigation pane.
  4. Select the appropriate 
    application pool name
     node and enable the 
     check box in the 
    General Configuration
     section to activate the application pool monitoring.
  5. Activate the required monitoring counters of the application pool.
  6. Click 
    The probe starts retrieving values for the selected counters to generate alarms and QoS.
CA recommends you to not monitor the Application Pool 
 from the list of application pools that are discovered.
Configure Monitors
The monitors are counters to measure data, based on the number, size, duration, and rate of data requested or received. You can configure the monitor properties to generate corresponding QoS and alarm messages. 
Follow these steps:
  1. Navigate to the required node.
  2. Specify the following field values:
      Publish Alarms
      : enables you to publish alarm messages.
      : activates the monitoring of the counter.
      : specifies the counter value that is compared with the specified threshold and is included in the QoS data. You can select from the following options:
        Current Value: 
         compares the last measured value with the 
        Threshold Value
        Compute Average:
         calculates the average of the values as measured in the given time interval. 
      : specifies operator to compare the threshold value. 
      : specifies the alarm threshold value. If the value is breached, the probe generates an alarm message.
      Alarm message
      : specifies the alarm message to be generated.
  3. Click 
View Message Pool
You can view the properties of alarm messages that are configured in the probe.
Follow these steps:
  1. Click the 
  2. Navigate to the 
     section and select the required message.
    The following fields display the configured values of the selected alarm message:
       indicates the name associated with the selected alarm message.
       indicates the checkpoint used for monitoring the probe.
      : indicates the severity of the selected alarm message.
      Error Alarm Message
      : indicates the alarm message for error situation.
      Clear Alarm Message
      : indicates the clear message for alarm.
      : indicates the alarm subsystem ID that defines the alarm source.
      Error Token
      : indicates the token for error situation.
      OK Token
      : indicates the token for clear alarm situation.