IIS Probe - Monitoring & Reporting - more questions

book

Article ID: 196287

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

This case is being opened in order to continue analyzing few remaining concerns after the documents and data provided under case#32117094.   

2. Performance Counters

There is a pretty good overview about Perfmon alternatives on "Windows Performance Counters Explained" (http://www.appadmintools.com/documents/windows-performance-counters-explained/), but unfortunately, in relation to IIS, it is only showing alternatives for Webservices increased/decreased load, user connections, or http requests, but nothing related to the IIS queues themselves. 

Anyway, by looking into other articles and loose data you have shared, I have found what I believe to be the closer option we have at the moment, that could provide IIS queues performance related reports, through the following ASP counters. 

a. "QOS_ASP_REQUESTS_QUEUED" (To be used to gather IIS queue length)
- Monitors the total number of ASP requests that are currently queued to be serviced. The number of requests waiting for service from the queue. 
 
b. "QOS_ASP_REQUESTS_WAITTIME" (To be used to gather average time in an IIS queue, request wait times)
- Monitors the time period up to which the last ASP request is queued. Number of milliseconds that the most recent ASP request was waiting in the queue.

* I have found a lot of detailed information about what do each performance metrics and counters do, but I am still a little bit uncertain about the steps to follow in order to have performance data collecting enabled. Apart from the pre-requisites at the IIS server level described above, what else should be done at the probe level in order to start collecting specific data, such as "QOS_ASP_REQUESTS_QUEUED" and "QOS_ASP_REQUESTS_WAITTIME"? 

3. Probes settings

a. Perfmon probe IM config
I have changed the settings to match those values that you have shown on the KB article. As I have been doing this on our Pre-Prod environment, when finally moving to Prod and configuring the probe on the actual IIS server, should I set a specific privileged user and password (provided by IIS support team), so that the probe have the right permissions to access IIS data? Or would it just be enough with an Administrator user at UIM level?

b. IIS probe IM config
I have not found very useful information at IM level, so I have try going through the AC.

c. IIS probe AC config
I was wondering how can I enable "Requests Queued" and "Requests_Waittime" data gathering, after all the pre-requisites are given. I am not even seeing an entry to include the specific url.

Cause

- guidance

Environment

Release : 9.0.2

Component : UIM - IIS

Resolution

2. Performance Counters

There is a pretty good overview about Perfmon alternatives on "Windows Performance Counters Explained" (http://www.appadmintools.com/documents/windows-performance-counters-explained/), but unfortunately, in relation to IIS, it is only showing alternatives for Webservices increased/decreased load, user connections, or http requests, but nothing related to the IIS queues themselves. 

Anyway, by looking into other articles and loose data you have shared, I have found what I believe to be the closer option we have at the moment, that could provide IIS queues performance related reports, through the following ASP counters. 

a. "QOS_ASP_REQUESTS_QUEUED" (To be used to gather IIS queue length)
- Monitors the total number of ASP requests that are currently queued to be serviced. The number of requests waiting for service from the queue. 
 
b. "QOS_ASP_REQUESTS_WAITTIME" (To be used to gather average time in an IIS queue, request wait times)
- Monitors the time period up to which the last ASP request is queued. Number of milliseconds that the most recent ASP request was waiting in the queue.

* I have found a lot of detailed information about what do each performance metrics and counters do, but I am still a little bit uncertain about the steps to follow in order to have performance data collecting enabled. Apart from the pre-requisites at the IIS server level described above, what else should be done at the probe level in order to start collecting specific data, such as "QOS_ASP_REQUESTS_QUEUED" and "QOS_ASP_REQUESTS_WAITTIME"? 

>>>QOS_ASP_REQUESTS_QUEUED and QOS_ASP_REQUESTS_WAITTIME are part of the ASP configuration. After you follow the IIS configuration, and activate the ASP counters, once you see values being collected, you can configure (enable) the QOS/alarms.

3. Probes settings

a. Perfmon probe IM config
I have changed the settings to match those values that you have shown on the KB article. As I have been doing this on our Pre-Prod environment, when finally moving to Prod and configuring the probe on the actual IIS server, should I set a specific privileged user and password (provided by IIS support team), so that the probe have the right permissions to access IIS data? Or would it just be enough with an Administrator user at UIM level?

>>>Yes, its not necessary but ideally I would ask them to setup a separate, specific privileged user and password for the Windows domain.

b. IIS probe IM config
I have not found very useful information at IM level, so I have try going through the AC.

>>>Either Admin Console or IM should work.

c. IIS probe AC config
I was wondering how can I enable "Requests Queued" and "Requests_Waittime" data gathering, after all the pre-requisites are given. I am not even seeing an entry to include the specific url.

>>>Please refer to and select the IIS Server->Host Configuration to configure the url, and click on ASP to see those counters and configuration parameters.

Additional Information

Metabase Compatibility Support appears to be applicable ONLY to legacy iis script and applications so if you have none, it's most likely irrelevant.
 

- Now, in relation to IIS Probe config, are we only capable of configuring only 1 URL per probe/server to perform reporting at a time?
Yes, one instance/url per probe.

- At this instance, I guess I should set a Windows username/password that is privileged to have access to that specific url right?
Yes, recommended.

- Once I configure all ASP pre-requisites along with below settings, I should be able to evidence the data gathering through the perfmon probe right?
Yes but you can check the iis probe ​​log itself.