Performance Monitor includes many counters that monitor connections. The counters on the TCP object are the best indicators of the success of connection requests.
The counters on the HTTP Service, FTP Server, and Gopher Service performance objects monitor connections maintained by each IIS service. The counters on these objects display only successful connection requests. They do not display failed attempts to connect to these IIS services. Like all counters at the Application Layer, they do not have information about connections until the connections are established. Performance Monitor counters that display the number of simultaneous connections maintained by Internet Information Server are discussed in Chapter 6, "Preventing Processor Bottlenecks."
The following table lists and describes the Performance Monitor counters that monitor the success and failure of connections to TCP.
Table 7.6 Performance Monitor Counters for Monitoring TCP Connection Successes and Failures
Counter | Indicates |
TCP: Connections Established | The number of simultaneous connections supported by TCP (at last observation). This counter displays the number of connections last observed to be in the ESTABLISHED or CLOSE-WAIT state. It displays the last observed value only; its value is not an average. |
TCP: Connection Failures | The number of connections that have failed since the service was started (regardless of when Performance Monitor was started). TCP counts a connection as having failed when it goes directly from sending (SYNC-SENT) or receiving (SYNC-RCVD) to CLOSED or from receiving (SYNC-RCVD) to listening (LISTEN). |
TCP: Connections Reset | The number of connections reset since the service was started (regardless of when Performance Monitor was started). TCP counts a connection as having been reset when it goes directly from ESTABLISHED or CLOSE-WAIT to CLOSED. |
These counters are included in IISNet.pmw, a Performance Monitor workspace file on the Supplement 1 CD.