CA Nimsoft Monitor Snap

Transcription

1 CA Nimsoft Monitor Snap Configuration Guide for IIS Server Monitoring iis v1.5 series

2 Legal Notices This online help system (the "System") is for your informational purposes only and is subject to change or withdrawal by CA at any time. This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This System is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between you and CA governing your use of the CA software to which the System relates (the CA Software ). Such agreement is not modified in any way by the terms of this notice. Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make one copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy. The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reason, it shall be your responsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS SYSTEM AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The manufacturer of this System is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Legal information on third-party and public domain software used in the Nimsoft Monitor solution is documented in Nimsoft Monitor Third-Party Licenses and Terms of Use (

3 Contents Chapter 1: Overview 5 About This Guide... 5 Related Documentation... 5 Preconfiguration Requirements... 5 Prerequisites... 6 Supported Platforms... 6 Installation Notes... 6 iis Server Configuration... 7 Chapter 2: Configuration Details 13 iis Node Host-<Host Name> Node Configure a Node Add Host Delete Host Chapter 3: QoS Threshold Metrics 23 iis QoS Metrics iis Alert Metrics Default Settings Configure Dynamic Alarm Thresholds Contents 3

4 Documentation Changes This table describes the version history for this document. Version Date What's New? 1.6 January 2014 Initial web-based GUI version of this probe. (Previous versions of this probe are configured using Infrastructure Manager). 4 Configuration Guide for IIS Server Monitoring

5 Chapter 1: Overview The Monitor for Internet Information Servers probe performs HTTP GET queries to the selected Microsoft IIS servers. The probe then transforms the query result into alarms and/or quality of service for SLA purposes. You can configure the profile for integrating the device seamlessly into the CA Nimsoft monitoring solution. This section contains the following topics: About This Guide (see page 5) Related Documentation (see page 5) Preconfiguration Requirements (see page 5) About This Guide This guide is for the CA Nimsoft Monitor Snap Administrator to help understand the configuration of the IIS Server Monitoring probe. This guide contains the following information: An overview of the IIS Server Monitoring probe. The related documentation for previous probe versions, release notes, and so on. The configuration details of the probe including information for the fields that are required to configure the probe. The common procedures that can be used in the probe configuration. Important! The field description for intuitive terms in the GUI has not been included in the document. Related Documentation For related information that may be of interest, see the following material: Related Documentation The Release Notes for the iis probe (IIS Server Monitoring) Preconfiguration Requirements This section contains the prerequisites, supported platforms, and installation notes for the IIS Server Monitoring probe. Chapter 1: Overview 5

6 Preconfiguration Requirements Prerequisites The Performance Collector probe must be deployed before deploying the IIS Server Monitoring probe. Supported Platforms Refer to the Nimsoft Compatibility Support Matrix for the latest information on supported platforms. See also the Support Matrix for Nimsoft Probes for specific information on the IIS Server Monitoring probe. Installation Notes You can install the IIS Server Monitoring probe for monitoring the IIS server. Follow these steps: 1. Install the package into your local archive. 2. Drop the package from your local archive onto the targeted robot. 3. Provide admin access to the iis probe in the Infrastructure Manager by using the Security > Probe Administration option. 4. A restart of the Performance Collector probe is needed for an IIS probe upgrade. 5. If the probe is running locally on the IIS server computer, you can use 'localhost' as the hostname to skip the performance authentication. 6. Double-click the probe for the initial configuration. 7. For remote monitoring, make sure that the remote registry is enabled on the IIS server. Installation notes for IISRequest.dll The IISRequest.dll is an ISAPI filter add-on for the IIS server and used by the IIS Server Monitoring probe. The IIS Server Monitoring probe request add-on supports several versions of the IIS server and Operating Systems. You can go through the readme.txt file for supported versions and for details about how to add this functionality. After the probe installation, the readme.txt is typically available at C:\Program Files\Nimsoft\Applications\iis location. 6 Configuration Guide for IIS Server Monitoring

7 Preconfiguration Requirements Installing ISAPI filter on a 64-bit OS If the IIS web server is running on a 64-bit version of Windows, the IISRequestNM64.dll or IISRequest64.dll library file is used. You must have the Microsoft Visual C Redistributable Package on the server running IIS (web server, not probe). The link to download this package is: 3-D6ACABD5D13B&displaylang=en Activating the ASP Counters on IIS 7 or above Refer to the following link: Installing Metabase Compatibility Support on IIS 7 or above The IIS Server Monitoring probe displays a wrong status for IIS 7 local server. To get the correct status, probe requires metabase, which is by default disabled on IIS 7 server. To install it, use the follow the link: iis Server Configuration The IIS Server Monitoring probe allows you to view IIS server data (requests) in a separate window. To enable this functionality, some configuration tasks must be done on the computer running the IIS server software. Further, the remote registry service must be running on the computer that is running the IIS server software. When the IIS Server Monitoring probe package is distributed to the robot, the following two files are copied to the..\nimsoft\probes\application\iis folder: IISRequest.dll IISRequest.cfg Follow these steps: 1. Create a folder on the computer running the IIS server, for example, C:\Inetpub\wwwroot\myserver\IISRequest. 2. Copy the files IISRequest.dll and the IISRequest.cfg to this folder. Chapter 1: Overview 7

8 Preconfiguration Requirements 3. Edit the IISRequest.cfg as follows: The first line is the host name of the computer where the IIS Server Monitoring probe is running (probe machine). The second line is the host name of the IIS server computer (IIS server machine). The port number is in the last line, by default it is 999. Note: This third line specifies the port that is used for the communication between the IIS Request filter on the IIS Server and the probe. If you change to another port number other than 999, enter this port number in the iis.cfg file (typically located in c:/program files/nimsoft/probes/iis). You can enter this port number as an extra line in the setup section: filterport = <portnumber> and it has to be identical in the IISRequest.cfg file. Open the IIS server console: Select Properties from the individual web site. 8 Configuration Guide for IIS Server Monitoring

9 Preconfiguration Requirements Select the ISAPI Filters tab and click the Add button. Enter the filter name and browse to add the IISRequest.dll. Click OK to add the filter. Click Apply in the Properties dialog and activate the filter. Chapter 1: Overview 9

10 Preconfiguration Requirements Check that the filter is active: 4. Check that a log file named IISRequest.log is generated in the folder containing the IISRequest.dll file. The first line in the log file must be **Started IISRequest**. 5. Check the output from the filter in the IIS Server Monitoring probe GUI. Note: The hourly statistics are available after one hour. Request data are sent to the IIS Server Monitoring probe each minute. Note for installing the ISAPI filter on a 64-bit OS: If the IIS web server is running on 64-bit Windows, it is necessary to have the Microsoft Visual C Redistributable Package on the server. You can download this package from the following link: D6ACABD5D13B&displaylang=en IISRequest: Provides status and statistics on IIS requests. Files: IISRequest.dll An IIS ISAPI filter add-on for the IIS Server Monitoring probe. For IIS 5, 5.1, 6 on Windows Server 2003, Windows XP. Not tested against the earlier IIS versions. 10 Configuration Guide for IIS Server Monitoring

11 Preconfiguration Requirements IISRequest64.dll An IIS ISAPI filter add-on for the IIS Server Monitoring probe. For IIS 5, 5.1, 6 on 64-bit version of Windows Server 2003 and Windows XP. Not tested against the earlier IIS versions. IISRequestNM.dll A Native Managed add-on module for the IIS Server Monitoring probe. For IIS 7, on Windows Vista. This module works the same way as the IIS ISAPI filter. IISRequestNM64.dll A Native Managed add-on module for the iis probe. For IIS 7, on 64-bit versions of Windows Vista. This module works the same way as the IIS ISAPI filter. Note: Any one of these DLLs is used on the IIS server, which is based on the version of Windows and IIS server. The steps that are required to use the IISRequest.dll file are as follows: 1. Locate the IISRequest.dll, IISRequest.cfg, and the IISRequest.log files on the computer on which IIS Server Monitoring probe is deployed. The typical location is C:\Program Files\Nimsoft\probes\application\iis folder. The files are available only after deploying the IIS Server Monitoring probe. 2. Create a folder on the computer running the IIS server, for example, C:\Inetpub\wwwroot\myserver\IISRequest and copy the IISRequest.dll, IISRequest.cfg and the IISRequest.log files to this folder. 3. Edit the IISRequest.cfg. The first line is the name of the computer on which the IIS Server Monitoring probe is running. The second line is the name of the IIS server computer. The last line is the port which is used to communicate between the add-on and the IIS Server Monitoring probe. The port number can be left at default value 999. If changed, the same port number is set at the IIS probe as well. See the IIS Server Monitoring probe configuration details. On WINDOWS XP, 2003: 1. Add necessary permissions to the IISRequest.cfg file by following these steps: Right-click the file and click the Security tab. Edit and add write access for the IIS_WPG user, or the user that is running the IISRequest.dll. Do the same for the IISRequest.log file. Add the filter: Open the IIS server console (IIS Manager), select properties from the individual web site, ISAPI filter and add. Enter a name (for example, IISR) and browse to add the IISRequest.dll. 2. Generate some traffic to the site. Check that the filter is active, and that entries are made in the IISRequest.log file in the dll folder. The first line in the log file must be **Started IISRequest**. Chapter 1: Overview 11

12 Preconfiguration Requirements On WINDOWS VISTA: 1. Add necessary permissions to the IISRequest.cfg file by following these steps: Right-click the file and click the security tab. Edit and add write access for the IIS_IUSRS user, or the user that is running the IISRequest.dll. Do the same for the IISRequest.log file. Register the module. For example, enter the name as IISR and change the IISRequest.dll to the version you are using ex. IISRequestNM64.dll. Do the registration from the IIS Manager GUI, on the top level, modules, add the native module, Register. After the registration, the module will start. The registration can also be done from the command line: From the windows\system32\inetsrv directory: appcmd install the module /name:iisr /image:c:\inetpub\wwwroot\myserver\iisrequest\iisrequest.dll. Important! Be careful with the path. A wrong path can lead to a nonfunctional web server and then a reset or restart is required for removing the module. 2. Generate some traffic to the site. From the IIS Manager GUI, check that the IISR module is loaded for the desired sites. Check that entries are made in the IISRequest.log file in the dll folder, the first line in the log file must be **Started IISRequest**. 3. Check the output from the filter in the IIS Server Monitoring probe GUI. The first hourly statistics are available after one hour. Request data are sent to the IIS Server Monitoring probe each minute. The IIS servers are defined in the IIS probe. The log files at the IIS server and the IIS probe can be inspected to verify correct operations. On IIS6 to IIS7.5, a restart of the IIS server is required, execute the command iisreset /restart, to properly reload the filter. For example, after an upgrade or a change to the cfg - configuration file. You can uninstall by removing or unregistering the module from the IIS manager. An unregistering at the web site level is done first. 12 Configuration Guide for IIS Server Monitoring

13 Chapter 2: Configuration Details This section contains configuration details specific to the IIS Server Monitoring probe. You can configure the probe to monitor the health and performance of the IIS Servers. The IIS Server Monitoring probe performs the HTTP GET queries to the selected Microsoft IIS servers. The probe then transforms the query result into alarms and/or quality of service for SLA purposes. This section contains the following topics: iis Node (see page 13) Configure a Node (see page 21) Add Host (see page 21) Delete Host (see page 21) iis Node This section contains configuration details specific to the IIS Server Monitoring probe. In this node, you can view the probe information and can configure the log properties of the IIS Server Monitoring probe. You can set the advanced properties of the probe to set maximum summary storage and number of concurrent threads. Navigation: iis Set or modify the following values that are based on your requirement: iis > Probe Information This section provides information about the probe name, probe version, start time of the probe, and the vendor who created the probe. iis > General Configuration This section allows you to configure the default log level for the probe. Log Level: Specifies the level of details that are written to the log file. Default: 3 - Info Chapter 2: Configuration Details 13

14 iis Node iis > Advanced Configuration This section allows you to set the maximum summary storage time and the number of concurrent threads for the probe. Max summary storage: Specifies the maximum data storage time from the drop-down list. This specified storage time is meant for local monitoring only and does not affect the QoS data. This value is the time range within which the monitored values are picked when calculating the average value (used when setting the alarm threshold). Default: 6 hours Maximum concurrent threads: Specifies the maximum number of profiles the probe can run simultaneously. The valid range is Default: 20 iis > Messages This section allows you to view the default alarm messages for the different error conditions. Error: Identifies the error message text. You can use variables by typing "$". The variables from the list as follows: state expected_state name display_name profile_name credential expected_credential restarts OK: Identifies the clear message text. Subsystem: Identifies a descriptive text name for the subsystem. iis > Options icon > Add New Host This section allows you to add a host for monitoring the IIS server. Hostname or IP address: Defines the name or IP address of the host to be monitored. Active: Activates the monitoring of the checkpoints on the host. Default: Selected Alarm Message: Specifies the alarm message to be issued when the host does not respond. Default: MsgAgentError 14 Configuration Guide for IIS Server Monitoring

15 iis Node Server address for http response: Specifies the address for testing the http response. For example, or Data collection interval (min): Specifies the data collection interval (how often to collect data from the host) from the drop-down list. Default: 1 Filter port: Specifies the port that is used to communicate between the add-on and the probe. The default value is 999. If changed, the same port number is set for the probe too. Default: 999 Windows username: Defines a valid user name with administrator privileges for logging in to the monitored host. Windows password: Defines the password for logging in to the monitored host. Windows domain: Defines the DNS domain name for locating the IIS server when it is not hosted on the local system. The blank field means that the system is hosting the IIS Server Monitoring probe. Http server authentication: Allows you to select one of the following authentication types: 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 values that are specified in Http username and Http password fields are used for the authentication. Windows: Uses the Windows authentication credentials as specified in Windows username and Windows password fields. Http username: Defines a valid user name with administrator privileges of the http server. Http password: Defines the password for logging in to the http server. Host-<Host Name> Node The Host-host name node displays information about the IIS host, which the IIS Server Monitoring probe is monitoring. The Host-host name node is displayed as a child node under the iis node. You can view information about the host name and the server address for http response. Note: All the hosts, appearing as child nodes, under the iis node are user-configurable. Hence, these hosts are referred as the Host-host name throughout this document. Chapter 2: Configuration Details 15

16 iis Node Navigation: iis > Host-host name Set or modify the following values that are based on your requirement: Host-host name > Host Configuration This section allows you to view and update the details of the IIS host, which the IIS Server Monitoring probe is monitoring. Hostname or IP address: Defines the name or IP address of the host to be monitored. Server address for http response: Specifies the address to be tested for http response. Host-host name > Options icon > Delete Host This option allows you to delete this host when you no longer want the probe to monitor it. <Host Name> Node The host name node represents the IIS host, which the IIS Server Monitoring probe is monitoring. The host name node is displayed as a child node under the Host-host name node. You can configure the properties of the host name node to generate alarms when the host does not respond. You can also configure the Windows credentials and Http server authentication details. Note: All the hosts, appearing as child nodes, under the Host-host name node are user-configurable. Hence, these hosts are referred as the host name throughout this document. Navigation: iis > Host-host name > host name Set or modify the following values that are based on your requirement: host name > Host Configuration This section allows you to configure the details of the host and also test the Windows credentials. Hostname or IP address: Defines the name or IP address of the host to be monitored. Active: Activates the monitoring of the checkpoints on the host. Default: Selected Alarm Message: Specifies the alarm message to be issued when the host does not respond. Default: MsgAgentError 16 Configuration Guide for IIS Server Monitoring

17 iis Node Server address for http response: Specifies the address for testing the http response. For example, or Description: Provides short description of the monitored host. Data collection interval (min): Specifies the data collection interval (how often to collect data from the host) from the drop-down list. Default: 1 Filter port: Specifies the port that is used to communicate between the add-on and the probe. The default value is 999. If changed, the same port number is set for the probe as well. Default: 999 Windows username: Defines a valid user name with administrator privileges for logging in to the monitored host. Windows password: Defines the password for logging in to the monitored host. Windows Domain: Defines the DNS domain name for locating the IIS server when it is not hosted on the local machine. The blank field means that the machine is hosting the IIS Server Monitoring probe. Http server Authentication: Allows you to select one of the following authentication types: 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 values that are specified in the Http username and Http password fields are used for the authentication. Windows: Uses the Windows authentication credentials as specified in Windows username and Windows password fields. Http username: Defines a valid user name with administrator privileges of the http server. Http password: Defines the password for logging in to the http server. host name > Actions > Test Windows Credentials This button in the Actions drop-down list allows you to test the response from the host using the specified Windows credentials. host name > Options icon > Activate All This option allows you to activate all the checkpoints for monitoring. host name > Options icon > Deactivate All This option allows you to deactivate all the checkpoints for monitoring. Chapter 2: Configuration Details 17

18 iis Node ASP Node The ASP node is used to configure the following checkpoints of the IIS server: Request Bytes In Total Requests Executing Requests Queued Navigation: iis > host name > ASP Set or modify the following values that are based on your requirement: ASP > Request Bytes In Total / Requests Executing / Requests Queued These sections allow you to configure the properties of the checkpoint for generating QoS message and alarms. QoS Name: Identifies the name of the QoS generated. Description: Provides a short description of the QoS. Units: Identifies the unit of the QoS. Metric Type Id: Identifies a unique id of the QoS. Publish Data: Triggers the generation of the QoS. Default: Not selected Note: Some checkpoints do not have a QoS name and therefore, unable to publish data. For such checkpoints, the QoS Name and Publishing Data fields are not visible. Publish Alarms: Triggers the generation of the alarms. Default: Not selected Description: Provides a short description of the monitoring object. Class: Defines the checkpoint class, under which the checkpoint is classified. Default: Disabled Value: Specifies the checkpoint value. The available options are Last/Current Sample and Compute Average. Default: Last/Current Sample Compute Average Interval (min): Calculates the average of the values that are measured in the time interval that is selected from the drop-down list. This field is enabled only after selecting the Compute Average option in the Value field. Default: Disabled 18 Configuration Guide for IIS Server Monitoring

19 iis Node Alarm Message: Specifies the alarm message to be issued when the specified threshold value is breached. These messages are kept in the message pool. Default: MsgError IIS Node The IIS node is used to configure the following checkpoints of the IIS server: HTTP Response Time HTTP Response Value IIS Status Value IIS max request time Total Allowed Async I/O Requests URI Cache Flushes URI Cache Hits URI Cache Hits % URI Cache Hits/minute URI Cache Misses URI Cache Misses/minute Navigation: iis > Host-host name > host name > IIS Set or modify the following values that are based on your requirement: IIS > HTTP Response Time / HTTP Response Value / IIS Status Value / IIS max request time / Total Allowed Async I/O Requests / URI Cache Flushes / URI Cache Hits / URI Cache Hits % / URI Cache Hits/minute / URI Cache Misses / URI Cache Misses/minute These sections allow you to configure the properties of the checkpoint for generating QoS message and alarms. Note: The field descriptions for these sections are same as described in the ASP node. System Node The System node is used to configure the following checkpoints of the IIS server: Available Physical Memory Memory In Use Memory Usage NW Bytes Total/sec Chapter 2: Configuration Details 19

20 iis Node Total CPU Total Memory Navigation: iis > Host-host name > host name > System Set or modify the following values that are based on your requirement: System > Available Physical Memory / Memory In Use / Memory Usage / NW Bytes Total/sec / Total CPU / Total Memory These sections allow you to configure the properties of the checkpoint for generating QoS message and alarms. Note: The field descriptions for these sections are same as described in the ASP node. Webservices Node The Webservices node is used to configure the following checkpoints of the IIS server: Bytes Received/sec Bytes Sent/sec Bytes Total/sec Connection Attempts/sec Current Connections Get Requests/sec Measured Async I/O Bandwidth Usage Navigation: iis > Host-host name > host name > Webservices Set or modify the following values that are based on your requirement: Webservices > Request Bytes In Total / Requests Executing / Requests Queued These sections allow you to configure the properties of the checkpoint for generating QoS message and alarms. Note: The field descriptions for these sections are same as described in the ASP node. 20 Configuration Guide for IIS Server Monitoring

21 Configure a Node Configure a Node This procedure provides the information to configure a particular section within a node. Each section within the node allows you to configure the properties of the probe for monitoring the IIS servers. Follow these steps: 1. Select the appropriate navigation path. 2. Update the field information and click Save. The specified section of the probe is configured. The probe is now ready to monitor system metrics. Add Host You can add the IIS host server under the iis node to start monitoring of the server. You can then configure the host properties for monitoring the checkpoints on the host. You can generate alarms when the host does not respond. You can also check the Windows credentials for logging on to the monitored host. 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. Update the field information and click Submit. 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. Delete Host You can delete the IIS host server when you no longer want to monitor it. Follow these steps: 1. Click the Options icon next to the Host-host name node in the navigation pane. 2. Click the Delete Host option. The host is deleted from the navigation pane. Chapter 2: Configuration Details 21

22

23 Chapter 3: QoS Threshold Metrics Many CA Nimsoft Monitor probes ships with the default QoS threshold values set. These values provide an idea of the type of values to be entered in the fields and are not necessarily recommended best practice values. To aid in tuning thresholds and reducing false-positive alarms, this section describes the QoS metrics and provides the default QoS thresholds. This section contains the following topics: iis QoS Metrics (see page 23) iis Alert Metrics Default Settings (see page 24) Configure Dynamic Alarm Thresholds (see page 25) iis QoS Metrics This section contains the QoS metrics for the IIS Server Monitoring probe. Monitor Name Units Description QOS_ASYNCIO_BWUSAGE QOS_BYTESRECEIVD_PS QOS_BYTESSENT_PS QOS_BYTESTOTAL_PS QOS_CONNATTEMPTS_PS Measured Async I/O Bandwidth Usage Bytes received/sec Measured Async I/O Bandwidth Usage Web server bytes received per second Bytes sent/sec Web server bytes sent per second Bytes Total/sec Connection attempts/sec QOS_CPU_USAGE Percent CPU Usage QOS_CURRENTCONNECTS Current connections Web server bytes total per second Connection attempts per second Current connections QOS_DISK_USAGE Megabytes Disk Usage QOS_GET_REQUESTS_PS Get Requests/sec Get requests per second QOS_IIS_HTTPRESTIME Milliseconds http response time QOS_IIS_USEROBJ Value IIS User object Chapter 3: QoS Threshold Metrics 23

24 iis Alert Metrics Default Settings Monitor Name Units Description QOS_MEMAVPHY Megabytes Physical Memory available QOS_MEMORY_INUSE Percent Memory in Use % QOS_MEMORY_USAGE Megabytes Memory Usage QOS_MEMORYAVAILPHYS Megabytes Physical Memory available QOS_NETWORK_BTPS Bytes Total/sec Network interface bytes total per second QOS_WSC_CACHEHITSPC Cache hits Web service cache hits % QOS_WSC_CACHEHITSPM QOS_WSC_CACHEMISSPM Cache hits/minute Cache misses/minute Web service cache hits Web Service Cache Misses iis Alert Metrics Default Settings This section contains the alert metric default settings for the IIS Server Monitoring probe. QoS Metric Error Threshold Error Severity Description MsgAgentError - Critical The IIS is not running on host. MsgPerfHandleError - Minor Unable to obtain handle to Perfmon probe. MsgPerSelectedError - Warning Unable to extract performance counters. MsgHostAvailError - Warning Host is not available MsgWarning - Warning Message warning MsgError - Critical Message error 24 Configuration Guide for IIS Server Monitoring

25 Configure Dynamic Alarm Thresholds Configure Dynamic Alarm Thresholds Dynamic thresholds are configured at the QoS metric level in each probe that publishes an alarm for a QoS metric. Important! In order to create dynamic alarm thresholds, you must have the baseline_engine probe version 2.0 installed on the robot and configured. Follow these steps for each QoS metric where you want to configure dynamic thresholds: 1. Select a node in the tree to view any associated monitors and QoS metrics. 2. Select the monitor you want to modify in the table. 3. Select the Publish Data and Compute Baseline options to enable the Dynamic Alarm Thresholds section of the configuration. 4. Choose a threshold algorithm. There are three algorithms allowed for dynamic alarm thresholds: Note: You must indicate the direction for each algorithm, either increasing or decreasing. Scalar: Each threshold is a specific value from the computed baseline. Percent: Each threshold is a specific percentage of the computed baseline. Standard Deviation: Each threshold is a measure of the variation from the computed baseline. A large standard deviation indicates that the data points are far from the computed baseline and a small standard deviation indicates that they are clustered closely around the computed baseline. 5. Save your settings. Chapter 3: QoS Threshold Metrics 25