Performance Counters
This document describes Microsoft® Internet Security and Acceleration (ISA) Server 2006 performance counters. For information about specific counters, see the following topics:
- Firewall Engine Performance Counters
- H.323 Filter Performance Counters
- Cache Performance Counters
- Microsoft Firewall Service Performance Counters
- SOCKS Filter Performance Counters
- Web Proxy Performance Counters
- Compression Performance Counters
- DiffServ Performance Counters
For information about monitoring, see Performance Counter Monitoring.
Firewall Engine Performance Counters
The following table lists the performance counters for the Firewall Engine.
| Performance Counter | Description |
|---|---|
Active Connections |
The total number of active connections currently passing data. |
Connections/sec |
The number of new connections created per second. |
TCP Established Connections/sec |
The number of TCP connections newly established per second. A TCP connection is counted as established after the 3-way SYN handshake is completed successfully. |
Bytes |
The total number of bytes that passed through ISA Server. |
Bytes/sec |
The number of bytes passed through ISA Server per second. |
Packets |
The total number of packets inspected by ISA Server. |
Packets/sec |
The number of packets inspected by ISA Server per second. |
Allowed Packets |
The total number of packets that ISA Server allows to pass. |
Allowed Packets/sec |
The number of packets per second that ISA Server allows to pass. |
Dropped Packets |
The number of packets dropped by ISA Server. |
Dropped Packets/sec |
The number of packets dropped by ISA Server per second. |
Backlogged Packets |
The number of backlogged packets. |
H.323 Filter Performance Counters
The following table lists the performance counters for the H.323 filter.
| Performance Counter | Description |
|---|---|
Total H.323 Calls |
The total number of H.323 calls handled by the H.323 filter since the Microsoft Firewall service was started. |
Active H.323 Calls |
The number of H.323 calls that are currently active. |
Cache Performance Counters
The following table lists the performance counters for the ISA Server 2006 cache.
| Performance Counter | Description |
|---|---|
Disk Bytes Retrieve Rate (KB/sec) |
Measures the rate at which bytes of data are retrieved from the disk cache. This counter is similar to the Disk URL Retrieve Rate counter, but monitors bytes, rather than URLs. |
Disk Cache Allocated Space (KB) |
Measures how much space is being used by the disk cache. It will be equal to or less than the amount configured for the disk cache. |
Disk Content Write Rate (Writes/sec) |
Measures the number of writes per second to the disk cache for the purpose of writing URL content to the cache disk. |
Disk Failure Rate (Failures/sec) |
Measures the number of input/output (I/O) failures per second. An I/O failure occurs when ISA Server fails to read from or write to the disk cache. This counter, with the Total Disk Failures counter, clearly indicates disk cache problems. |
Disk URL Retrieve Rate (URL/sec) |
Measures how many URLs are sent to clients from the disk cache in one second. This is a useful counter to measure at peak and off-peak times to check how the disk cache is performing. It can be compared with the Memory URL Retrieve Rate counter to determine how cache disk and memory are being utilized. |
Max URLs Cached |
Measures the maximum number of URLs that have been stored in the cache. |
Memory Bytes Retrieved Rate (KB/sec) |
Measures the rate at which bytes of data are retrieved from the memory cache. This counter is similar to the Memory URL Retrieve Rate counter, but monitors bytes, rather than URLs. |
Memory Cache Allocated Space (KB) |
Measures how much space is being used by the memory cache. It should be equal to or less than the amount configured for the memory cache. |
Memory URL Retrieve Rate (URL/sec) |
Measures how many URLs are sent to clients from the memory cache in one second. This is a useful counter to measure at peak and off-peak times, to check how the memory cache is performing and whether available memory allocated for caching purposes is being used efficiently. |
Memory Usage Ratio Percent (%) |
Shows the percentage of the total amount of cache fetches that are from the memory cache. A high percentage may indicate that it is worthwhile allocating more available memory resources to the cache. A low percentage may indicate that memory resources may be better used elsewhere. |
Total Disk Bytes Retrieved (KB) |
Measures the cumulative number of disk bytes that have been retrieved from the disk cache. This counter, added to the Total Memory Bytes Retrieved counter, indicates the total number of bytes retrieved from the cache. |
Total Disk Failures |
Measures the number of times that Web proxy failed to read from or write to the disk cache due to an I/O failure. A low counter indicates that a disk is performing properly. A high counter indicates that a cache disk is too small, too slow, or corrupted. |
Total Disk URLs Retrieved |
Measures the cumulative number of URLs that have been retrieved from the disk cache. This counter, added to the Total Memory URLs Retrieved counter, indicates the total number of URLs retrieved from the cache. |
Total Memory Bytes Retrieved (KB) |
Measures the cumulative number of memory bytes that have been retrieved from the memory cache in response to client requests to the cache. A low number might indicate that memory resources dedicated to the cache are not being used efficiently. A high number might indicate that more memory resources should be allocated to the cache. |
Total Memory URLs Retrieved |
Measures the cumulative number of URLs that have been retrieved from the memory cache in response to client requests to the cache. A low number might indicate that memory resources dedicated to the cache are not being used efficiently. A high number might indicate that more memory resources should be allocated to the cache. |
Total URLs Cached |
Measures the cumulative number of URLs that have been stored in the cache. If this counter and the URLs in Cache counter are low, it may indicate a problem with the cache. The cache may not be configured for optimal use or the cache size may be too small. |
URL Commit Rate (URL/sec) |
Indicates the speed at which URLs are being written to the cache. If the rate of this counter is comparable to the rate of the Disk Failure Rate counter, it indicates that a high proportion of attempts to write to the cache are failing. This could indicate a problem with cache configuration, a cache disk that is too slow, or a cache size that is too small. |
URLs in Cache |
Measures the current number of URLs in the cache. |
Cache Hit Percentage for Range Requests |
Shows the percentage of bytes served from cache for responses to Hypertext Transfer Protocol (HTTP) requests containing range headers. |
Bytes actually requested from server for range requests/Bytes in range requests |
Shows the percentage requested from the server for range requests out of the number of bytes in range requests when the cache rule enabled range request caching. |
Microsoft Firewall Service Performance Counters
The following table lists the performance counters for the Microsoft Firewall service.
| Performance Counter | Description |
|---|---|
Accepting TCP Connections |
The number of connection objects that wait for a TCP connection from Firewall clients. |
Active Sessions |
The number of active sessions for the Firewall service. |
Active TCP Connections |
The number of active TCP connections currently passing data. Connections pending or not yet established are counted elsewhere. |
Active UDP Connections |
The number of active User Datagram Protocol (UDP) connections. |
Available Worker Threads |
The number of Firewall service worker threads that are available or waiting in the completion port queue. |
Pending Back-Connecting TCP Connections |
The number of TCP connections awaiting an inbound connect call to complete. These are connections placed by the Firewall service to a client after the Firewall service accepts a connection from the Internet on a listening socket. |
Bytes Read/sec |
The number of bytes read by the data pump per second. |
Bytes Written/sec |
The number of bytes written by the data pump per second. |
Pending TCP Connections |
The number of TCP connections pending. These are connections awaiting completion between the Firewall service and remote computers. |
DNS Cache Entries |
The current number of Domain Name System (DNS) domain name entries cached as a result of Firewall service activity. |
DNS Cache Flushes |
The number of times that the DNS domain name cache has been flushed or cleared by the Firewall service. |
DNS Cache Hits |
The number of times a DNS domain name was found within the DNS cache by the Firewall service. |
DNS Cache Hits % |
The percentage of DNS domain names serviced by the DNS cache, from the total of all DNS entries that have been retrieved by the Firewall service. |
DNS Retrievals |
The number of DNS domain names that have been retrieved by the Firewall service. |
Failed DNS Resolutions |
The number of gethostbyname and gethostbyaddr application programming interface (API) calls that have failed. These are calls used to resolve host DNS domain names and IP addresses for Firewall service connections. |
Kernel Mode Data Pumps |
The number of kernel mode data pumps created by the Firewall service. |
Listening TCP Connections |
The number of connection objects that wait for TCP connections from remote Internet computers. |
Non-connected UDP mappings |
The number of mappings available for UDP connections. |
Pending DNS Resolutions |
The number of gethostbyname and gethostbyaddr API calls pending resolution. These are calls used to resolve host DNS domain names and IP addresses for Firewall service connections. |
SecureNAT Mappings |
The number of mappings created by SecureNAT. |
Successful DNS Resolutions |
The number of gethostbyname and gethostbyaddr API calls successfully returned. These are calls used to resolve host DNS domain names and IP addresses for Firewall service connections. |
Worker Threads |
The number of Firewall service worker threads that are currently active. |
SOCKS Filter Performance Counters
The following table lists the performance counters for the SOCKS filter .
| Performance Counter | Description |
|---|---|
Active Sessions |
A single SOCKS session includes the CONNECT and BIND commands for a single client. |
Active Connections |
The total number of active connections currently passing data. Connections pending or not yet established are not included. This counter is incremented when a SOCKS connection is established. A SOCKS connection is counted after a successful CONNECT command, when the SOCKS filter begins the data pump stage of the protocol. This counter is decremented when the connection is terminated (for any reason). |
Connecting Connections |
The number of SOCKS connections waiting for a remote computer to connect to. When a client sends a CONNECT command to the SOCKS filter, the SOCKS filter connects to the specified server on behalf of the client. This counter is incremented immediately before the SOCKS filter starts the connection process to the specified server, and is decremented when the connection (to the specified server) process is completed (successfully or unsuccessfully). |
Listening Connections |
The number of connection objects waiting for remote computers to connect. When a client sends a BIND command to the SOCKS filter, the SOCKS filter listens for an incoming connection on the specified port. This counter is incremented when the SOCKS filter starts waiting for the incoming connection, and is decremented when the incoming connection is received (or if the connection was terminated). |
Bytes Read/sec |
The number of bytes read on all SOCKS connections per second. The term "bytes read" refers to the amount of data from the client to the server during the data pump stage of the protocol. |
Bytes Written/sec |
The amount of data sent from the server to the client during the data pump stage of the protocol. |
Pending DNS Resolutions |
The number of pending name resolution requests. These requests resolve host DNS names and IP addresses for SOCKS connections. |
Successful DNS Resolutions |
The number of name resolution requests resolved each second. These requests resolve host DNS names and IP addresses for SOCKS connections. |
Web Proxy Performance Counters
The following table lists the performance counters for the Web proxy.
| Performance Counter | Description |
|---|---|
Active Web Sessions |
Indicates how many clients are currently running Web proxy. Monitoring this counter at both peak and off-peak times gives a good indication of server usage. The configuration setting for maximum Web request connections influences this value. This counter may also be useful if you need to temporarily stop ISA Server services. When authentication does not take place, all of the clients from a single IP address are viewed as one session. |
Array Bytes Received/sec (Enterprise) |
The rate at which data bytes are received from other ISA Server computers within the same array. |
Array Bytes Sent/sec (Enterprise) |
The rate at which data bytes are sent to other ISA Server computers within the same array. |
Array Bytes Total/sec (Enterprise) |
The sum of the Array Bytes Sent/sec and the Array Bytes Received/sec counters. This is the total rate for all data bytes transferred between the ISA Server computer and other members of the same array. |
Average Milliseconds/request |
The mean number of milliseconds required to service a Web Proxy client request, not including requests serviced by the Secure Sockets Layer (SSL) tunnel. This counter can be monitored at peak and off-peak times to get a comprehensive picture of how fast client requests are being serviced. A counter with a value that is too high might indicate that the ISA Server computer is having difficulty in handling all requests and that requests are being delayed. |
Average request speed |
The average speed of the request for all requests in the previous minute. The speed is calculated by dividing the request size by the time needed to serve the request, and is provided in bytes per second. |
Bytes actually requested from server for range requests/Bytes in range requests (%) |
The percentage requested from the server for range requests out of the number of bytes in range requests when the cache rule enabled range request caching. |
Bytes Requested from Server in Ranges |
The total number of bytes requested from the server in HTTP requests containing range headers. |
Bytes Served from Cache in Ranges |
The total number of bytes returned in responses to HTTP requests containing range headers served from cache. |
Bytes Served (Last Hour) From Cache in Ranges |
The total number of bytes returned in responses to HTTP requests containing range headers served from cache in the last hour. |
Bytes Served (Last Hour) in Ranges |
The total number of bytes returned in responses to HTTP requests containing range headers in the last hour. |
Bytes Served in Ranges |
The total number of bytes returned in responses to HTTP requests containing range headers. |
Cache Hit Ratio (%) |
Determines how many Web Proxy client requests have been served using cached data (Total Cache Fetches), as a percentage of the total number of successful Web Proxy client requests to the ISA Server computer (Total Successful Requests). Its value gives a good indication of the effectiveness of the cache. A high counter value indicates that a high level of requests are being serviced from the cache, meaning faster response times. A zero counter value indicates that caching is not enabled. A low counter value may indicate a configuration problem. The cache size may be too small, or requests may not be cacheable. |
Cache Hit Percentage for Range Requests |
The percentage of bytes served from cache for responses to HTTP requests containing range headers. |
Cache Hit Ratio for the Last 10k Requests (%) |
The amount of requests served from the cache as a percentage of total successful requests serviced. This ratio is the same as that measured by the Cache Hit Ratio counter. The difference between these two counters is that the Cache Running Hit Ratio counter measures this ratio for the last 10,000 requests serviced, and the Cache Hit Ratio counter measures this ratio since the last time that Web proxy was started. This means that the Cache Running Hit Ratio counter gives a more dynamic evaluation of cache effectiveness. |
Client Bytes Received/sec |
The rate at which data bytes are received from Web Proxy clients. The value changes according to the volume of Web Proxy client requests, but a consistently slow rate may indicate a delay in servicing requests. |
Client Bytes Sent/sec |
The rate at which data bytes are sent to Web Proxy clients. The value changes according to the volume of Web Proxy client requests, but a consistently slow rate may indicate a delay in servicing requests. |
Client Bytes Total/sec |
The sum of the Client Bytes Sent/sec and the Client Bytes Received/sec counters. This is the total rate for all bytes transferred between the ISA Server computer and Web Proxy clients. |
Connect Errors |
The total number of errors that occurred while connecting. |
Connect Errors/Total Errors (%) |
The percentage of errors that occurred while connecting as a ratio of the total number of failed requests during the time shown in the duration field. |
Current Array Fetches Average (Milliseconds/request) |
The mean number of milliseconds required to service a Web Proxy client request that is fetched through another array member. This does not include requests for services by the SSL tunnel. |
Current Cache Fetches Average (Milliseconds/request) |
The mean number of milliseconds required to service a Web Proxy client request from the cache. This does not include requests for services by the SSL tunnel. |
Current Direct Fetches Average (Milliseconds/request) |
The mean number of milliseconds required to service a Web Proxy client request directly to the Web server or upstream proxy. This does not include requests for services by the SSL tunnel. |
Failing Requests/sec |
The rate of Web Proxy client requests that have been completed with some type of error. This counter can be compared with the Requests/sec counter to give an indication of how well ISA Server is servicing incoming Web requests. A high failure rate, as compared with the rate of incoming requests, suggests that ISA Server is having difficulty in coping with all incoming requests. Connection settings for incoming Web requests may be incorrectly configured, or connection bandwidth may be insufficient. |
Failing Requests/Total Requests (%) |
The percentage of failing requests out of the total number of requests during the time shown in the duration field. |
FTP Requests |
The number of File Transfer Protocol (FTP) requests that have been made to Web proxy. A consistently low counter value may influence the caching policy for FTP objects. |
HTTP Requests |
The number of HTTP requests that have been made to Web proxy. |
HTTPS Sessions |
The total number of Secure Hypertext Transfer Protocol (HTTPS) secured sessions serviced by the SSL tunnel. |
Incoming Connections/sec |
The rate of incoming connections (per second). |
IO Errors to Client |
The total number of input/output errors that occurred during communication with the client. |
IO Errors to Client/Total Errors |
The percentage of input/output errors that occurred during communication with the client out of the total number of failed requests during the time shown in the duration field. |
IO Errors to Server |
The total number of input/output errors that occurred during communication with the server. |
IO Errors to Server/Total Errors (%) |
The percentage of input/output errors that occurred during communication with the server out of the total number of failed requests during the time shown in the duration field. |
IO Errors to Array Member |
The total number of input/output errors that occurred during communication with an array member. |
IO Errors to Array Member/Total Errors (%) |
The percentage of input/output errors that occurred during communication with an array member out of the total number of failed requests during the time shown in the duration field. |
Maximum Users |
The maximum number of users that have connected to Web proxy simultaneously. This counter can be useful for determining load usage and license requirements. |
Memory Pool for HTTP Requests (%) |
Percentage of memory available for HTTP requests. When an HTTP request is made, ISA Server uses memory from a pre-allocated pool. You can use the ProxyVmemAlloc3pSize registry value in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3Proxy\Parameters registry key to modify the size of this pool. |
Memory Pool for SSL Requests (%) |
Percentage of memory available for SSL requests. When an SSL request is made, ISA Server uses memory from a pre-allocated pool. You can use the ProxyVmemAlloc1pSize registry value in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3Proxy\Parameters registry key to modify the size of this pool. |
Outgoing Connections/sec |
The rate of outgoing connections (per second). |
Requests/sec |
The rate of incoming requests that have been made to Web proxy. A higher value means that more ISA Server resources will be required to service incoming requests. |
Requests from Array Member (Enterprise) |
The total number of requests coming from another array member. |
Requests from Array Member/Total Errors (%)(Enterprise) |
The percentage of requests coming from another array member out of the total number of failed requests during the time shown in the duration field. |
Requests to Array Member (Enterprise) |
The total number of requests going to another array member. |
Requests to Array Member/Total Errors (%)(Enterprise) |
The percentage of requests going to another array member out of the total number of failed requests during the time shown in the duration field. |
Requests with Keep Alive to Client |
The total number of requests that use an existing keep alive connection between the client and ISA Server. |
Requests with Keep Alive to Client/Total Errors (%) |
The percentage of requests that use an existing keep alive connection between the client and ISA Server as a ratio of the total number of failed requests during the time shown in the duration field. |
Requests with Keep Alive to Server |
The total number of requests that use an existing keep alive connection between ISA Server and the Web server. |
Requests with Keep Alive to Server/Total Errors (%) |
The percentage of requests that use an existing keep alive connection between ISA Server and the Web server as a ratio of the total number of failed requests during the time shown in the duration field. |
Requests with Keep Alive to Array Member |
The total number of requests that use an existing keep alive connection between ISA Server and another array member. |
Requests with Keep Alive to Array Member/Total Errors (%) |
The percentage of requests that use an existing keep alive connection between ISA Server and another array member out of the total number of failed requests during the time shown in the duration field. |
Requests with Multiple Ranges |
The number of requests with more than one range in the HTTP Range header. |
Reverse Bytes Received/sec |
The rate at which data bytes are received by Web proxy from Web publishing servers in response to incoming requests. This rate can be monitored at peak and off-peak times as an indication of how ISA Server is performing in servicing incoming Web requests. |
Reverse Bytes Sent/sec |
The rate at which data bytes are sent by Web proxy to Web publishing servers in response to incoming requests. This rate can be monitored at peak and off-peak times as an indication of how ISA Server is performing in servicing incoming Web requests. |
Reverse Bytes Total/sec |
The total sum of the Reverse Bytes Sent/sec and the Reverse Bytes Received/sec counters. This is the total rate for all bytes transferred between Web proxy and Web publishing servers in response to incoming requests. |
Sites Allowed |
The total number of Internet sites to which Web proxy has denied access. An excessively high number might indicate an access policy that is too restrictive. |
Sites Denied |
The total number of Internet sites to which Web proxy has granted access. This can be compared with the Site Access Denied counter to give a numeric summary of the results of access policy configuration. |
SNEWS Sessions |
The total number of SNEWS sessions serviced by the SSL tunnel. |
SSL Client Bytes Received/sec |
The rate at which SSL data bytes are received by Web proxy from SSL clients. Similar to the Client Bytes Received/sec counter, but counts only SSL requests. |
SSL Client Bytes Sent/sec |
The rate at which SSL data bytes are sent by Web proxy to SSL clients. Similar to the Client Bytes Sent/sec counter, but counts only SSL requests. |
SSL Client Bytes Total/sec |
The sum of the SSL Client Bytes Sent/sec and the SSL Client Bytes Received/sec counters. This is the total rate for all bytes transferred between Web proxy and SSL clients. |
Thread Pool Active Sessions |
The number of sessions being actively serviced by thread pools. |
Thread Pool Failures |
The number of requests rejected because the thread pool was full. |
Thread Pool Size |
The number of threads in the thread pool. This thread pool represents the resources available to service client requests. |
Total Array Fetches (Enterprise) |
The total number of Web Proxy client requests that have been served by requesting the data from another ISA Server computer within this array. These requests are the result of the Cache Array Routing Protocol (CARP) algorithm, which randomly stores objects in any one of the member servers cache. This counter is influenced by the cache size for each ISA Server computer in the array, because a server with a larger cache holds more cache items. The load factor for each server can also be configured, to determine how workload is divided among array members. |
Total Cache Fetches |
The total number of Web Proxy client requests that have been served by using cached data. A high number indicates a cache being fully exploited. |
Total Failing Requests |
The total number of requests that have failed to be processed by Web proxy due to errors. Errors can be the result of Web proxy failing to locate a requested server URL on the Internet or because the client did not have authorized access to the requested URL. This counter should be lower than the Total Successful Requests counter. If not, it is an indication that ISA Server is failing to service requests effectively. This could be a configuration problem, or a connection that is too slow. It could also indicate an access policy that is too restrictive. |
Total Pending Connects |
The total number of pending connections to Web proxy. |
Total Requests |
The total number of requests that have been made to Web proxy. It is the sum of the Total Successful Requests and the Total Failed Requests counters. |
Total Reverse Fetches |
The total number of incoming requests that have been served by requesting the data from Web publishing servers. |
Total SSL Sessions |
The total number of SSL sessions serviced by the SSL tunnel. |
Total Successful Requests |
The total number of requests that have been successfully processed by Web proxy. This counter can be compared with the Total Requests and the Total Failed Requests counters to indicate the effectiveness of ISA Server in servicing requests. |
Total Upstream Fetches |
The total number of requests that have been served by using data from the Internet or from a chained proxy computer. This counter can be compared to the Total Cache Fetches counter to determine what proportion of requests are being serviced from remote servers on the Internet or upstream proxies, compared with those being serviced from the cache. |
Total Users |
The total number of users that have connected to Web proxy. It represents a history of past server usage. |
Unknown SSL Sessions |
The total number of unknown SSL sessions serviced by the SSL tunnel. |
Upstream Bytes Received/sec |
The rate at which data bytes are received by Web proxy from remote servers on the Internet or from a chained proxy computer in response to requests from Web proxy. The value of this counter depends partially on the connection bandwidth. If the counter value is consistently low, it may indicate a bottleneck caused by a slow connection. Changing the bandwidth priority configuration may help in this situation, or a faster connection may be required. |
Upstream Bytes Sent/sec |
The rate at which data bytes are sent by Web proxy to remote servers on the Internet or to a chained proxy computer. The value of this counter depends partially on the connection bandwidth. If the counter value is consistently low, it may indicate a bottleneck caused by a slow connection. Changing the bandwidth priority configuration may help in this situation, or a faster connection may be required. |
Upstream Bytes Total/sec |
The sum of the Upstream Bytes Sent/sec and the Upstream Bytes Received/sec counters. It represents the total rate for all bytes transferred between Web proxy and remote servers on the Internet or a chained proxy server. |
Compression Performance Counters
The following table lists the performance counters for HTTP compression.
| Performance Counter | Description |
|---|---|
Compression - Responses Compressed: Accumulated Ratio |
The percentage of HTTP responses compressed by ISA Server out of the total number of HTTP requests handled by ISA Server. |
Compression - Current Ratio of Responses Compressed |
The percentage of HTTP responses compressed by ISA Server out of the number of HTTP requests handled by ISA Server, during the sample period. |
Compression - Ratio of Size Reduction |
For HTTP responses compressed by ISA Server, the average size reduction of the HTTP response body as a percentage of the uncompressed body size. |
Compression - Current Compression Ratio |
For HTTP responses compressed by ISA Server, the average size reduction of the HTTP response body as a percentage of the uncompressed body size, during the sample period. |
Compression - Total Failures |
The total number of failures to compress or decompress a response. |
Compression - Responses Decompressed: Accumulated Ratio |
The percentage of HTTP responses decompressed by ISA Server out of the total number of HTTP requests handled by ISA Server. |
Compression - Current Ratio of Responses Decompressed |
The percentage of HTTP responses decompressed by ISA Server out of the number of HTTP requests handled by ISA Server, during the sample period. |
DiffServ Performance Counters
The following tables lists the performance counters for DiffServ.
| Performance Counter | Description |
|---|---|
DiffServ Requests - 1st Priority |
The total number of first priority requests since the last performance monitoring sample. |
DiffServ Requests - 2nd Priority |
The total number of second priority requests since the last performance monitoring sample. |
DiffServ Requests - 3rd Priority |
The total number of third priority requests since the last performance monitoring sample. |
DiffServ Requests - 4th Priority |
The total number of fourth priority requests since the last performance monitoring sample. |
DiffServ Requests - 5th Priority |
The total number of fifth priority requests since the last performance monitoring sample. |
DiffServ Requests - Lower Priority |
The total number of low priority requests (sixth priority and lower) since the last performance monitoring sample. |
DiffServ Requests - Total Priority |
The total number of requests with an assigned priority since the last performance monitoring sample. |
DiffServ Requests - Non-Priority |
The total number of requests without an assigned priority since the last performance monitoring sample. |
DiffServ Responses - 1st Priority |
The total number of first priority responses since the last performance monitoring sample. |
DiffServ Responses - 2nd Priority |
The total number of second priority responses since the last performance monitoring sample. |
DiffServ Responses - 3rd Priority |
The total number of third priority responses since the last performance monitoring sample. |
DiffServ Responses - 4th Priority |
The total number of fourth priority responses since the last performance monitoring sample. |
DiffServ Responses - 5th Priority |
The total number of fifth priority responses since the last performance monitoring sample. |
DiffServ Responses - Lower Priority |
The total number of low priority responses (sixth priority and lower) since the last performance monitoring sample. |
DiffServ Responses - Total Priority |
The total number of responses with an assigned priority since the last performance monitoring sample. |
DiffServ Responses - Non-Priority |
The total number of responses without an assigned priority since the last performance monitoring sample. |
DiffServ Requests - 1st Priority Ratio to Total |
The ratio of first priority requests to the total number of requests. |
DiffServ Requests - 2nd Priority Ratio to Total |
The ratio of second priority requests to the total number of requests. |
DiffServ Requests - 3rd Priority Ratio to Total |
The ratio of third priority requests to the total number of requests. |
DiffServ Requests - 4th Priority Ratio to Total |
The ratio of fourth priority requests to the total number of requests. |
DiffServ Requests - 5th Priority Ratio to Total |
The ratio of fifth priority requests to the total number of requests. |
DiffServ Requests - Low Priority Ratio to Total |
The ratio of low priority requests (sixth priority and lower) to the total number of requests. |
DiffServ Requests - Priority Ratio to Total |
The ratio of requests with an assigned priority to the total number of requests. |
DiffServ Requests - Non-Priority Ratio to Total |
The ratio of requests without an assigned priority to the total number of requests. |
DiffServ Responses - 1st Priority Ratio to Total |
The ratio of first priority responses to the total number of responses. |
DiffServ Responses - 2nd Priority Ratio to Total |
The ratio of second priority responses to the total number of responses. |
DiffServ Responses - 3rd Priority Ratio to Total |
The ratio of third priority responses to the total number of responses. |
DiffServ Responses - 4th Priority Ratio to Total |
The ratio of fourth priority responses to the total number of responses. |
DiffServ Responses - 5th Priority Ratio to Total |
The ratio of fifth priority responses to the total number of responses. |
DiffServ Responses - Lower Priority Ratio to Total |
The ratio of low priority responses (sixth priority and lower) to the total number of responses. |
DiffServ Responses - Priority Ratio to Total |
The ratio of responses with an assigned priority to the total number of responses. |
DiffServ Responses - Non-Priority Ratio to Total |
The ratio of responses without an assigned priority to the total number of responses. |
Performance Counter Monitoring
This topic contains some suggestions regarding which performance counters to monitor for load monitoring and security monitoring.
Load Monitoring
To monitor general performance, closely monitor the following counters.
| Performance Counter | Description |
|---|---|
ISA Server Firewall Engine |
Active Connections |
ISA Server Firewall Service |
Active Sessions |
ISA Server Web Proxy |
Requests/sec |
ISA Server Firewall Engine |
Bytes/sec |
Security Monitoring
To monitor general security threats, closely monitor the following counters.
| Category | Performance Counter Name |
|---|---|
ISA Server Firewall Engine |
Dropped packets/sec |
ISA Server Firewall Engine |
Packets/sec |
ISA Server Firewall Engine |
Connections/sec |
ISA Server Web Proxy |
Average Milliseconds/request |