You can use the Windows NT Performance Monitor utility to monitor your server's performance. Performance Monitor contains counters that monitor the activity of specific objects, that is, specific services or mechanisms controlling server resources. Counters monitor activity that varies over time, such as file transfer rates, bandwidth usage, or connection rates. For detailed information about using the Performance Monitor tool itself, see the Windows NT documentation.
Windows NT includes a number of counters, and IIS installs special counters, including Web service counters, FTP service counters, and global counters for Internet Information Services. This topic lists and describes the FTP service counters.
Note While adding counters in the Add To dialog box in Performance Monitor, you can view an explanation of the currently selected counter by clicking the Explain button.
Note To obtain and use counters related to TCP, see the Windows NT Resource Kit documentation. These counters, along with disk counters also provided by the Windows NT Resource Kit, can supplement the information obtained from the counters listed here.
Counters related to bandwidth usage for FTP are listed below. To view these counters, follow the procedure outlined in Viewing Current Performance; for Object, select FTP Service, and for Instance select an instance or, to monitor all FTP sites at once, select _Total.
Counter | Description |
---|---|
Current Blocked Async I/O Requests | Current number of requests that are temporarily blocked by the bandwidth throttle setting. Blocked requests are held in a buffer and then unblocked if more bandwidth becomes available, unless a timeout limit is reached. |
Counters related to throughput are listed below. To view these counters, follow the procedure outlined in Viewing Current Performance; for Object, select FTP Service, and for Instance select an instance or, to monitor all FTP sites at once, select _Total.
Counter | Description |
---|---|
Bytes Received/sec | The rate at which data bytes are received by the FTP service at the Application Layer; does not include protocol headers or control bytes. |
Bytes Sent/sec | The rate at which data bytes are sent by the FTP service at the Application Layer; does not include protocol headers or control bytes. |
Bytes Total/sec | The rate at which data bytes are sent and received by FTP service at the Application Layer; does not include protocol headers or control bytes. Bytes Total/sec is the sum of Bytes Sent/sec plus Bytes Received/sec. |
Total Files Received | The total number of files received by the FTP service since the service started. |
Total Files Sent | The total number of files sent by the FTP service since the service started. |
Total Files Transferred | The total number of files transferred by the FTP service since the service started. Files Total is the sum of Files Sent plus Files Received. |
Counters related to connections, logons, and users are listed below. To view these counters, follow the procedure outlined in Viewing Current Performance; for Object, select FTP Service, and for Instance select an instance or, to monitor all FTP sites at once, select _Total.
Note For all counters monitoring connection activity, the counts are the total for all FTP sites, regardless of what you choose for Instance.
Counter | Description |
---|---|
Current Anonymous Users | The number of users who currently have an anonymous connection using the FTP service. If a client request for an anonymous connection is rejected and the client responds with valid authenticating data, the connection is counted as non-anonymous. |
Current Connections | The current number of connections established with the FTP service (sum of anonymous and non-anonymous users). The count is the current total for all FTP sites combined, regardless of what you choose for Instance. |
Current NonAnonymous Users | The number of users who currently have a non-anonymous connection using the FTP service. If a client request for an anonymous connection is rejected and the client responds with valid authenticating data, the connection is counted as non-anonymous. |
Maximum Anonymous Users | The maximum number of users who established concurrent anonymous connections using the FTP service (since service startup). |
Maximum Connections | The largest number of simultaneous connections established with the FTP service since service startup. The count is the maximum for all FTP sites combined, regardless of what you choose for Instance. |
Maximum NonAnonymous Users | The maximum number of users who established concurrent non-anonymous connections using the FTP service (since service startup). If a client request for an anonymous connection is rejected and the client responds with valid authenticating data, the connection is counted as non-anonymous. |
Total Anonymous Users | The total number of users who established an anonymous connection with the FTP service (since service startup). If a client request for an anonymous connection is rejected and the client responds with valid authenticating data, the connection is counted as non-anonymous. |
Total Connection Attempts |
The total number of connections to the FTP service that have been attempted since service startup. The count is the total for all FTP sites combined, regardless of what you choose for Instance. This number does not include connection attempts that failed at the TCP (transport) or IP (network) layer. To monitor all connection attempts, use the Connection counters on the TCP performance object; for information about obtaining and viewing this object, see the Windows NT Resource Kit. To monitor currently active connections, use Current Connections. |
Total Logon Attempts | The total number of successful logons to the FTP service since the service started; does not include failed logon attempts. To calculate failed attempts (where clients were able to connect but not log on), subtract Logon Attempts from Connection Attempts. |
Total NonAnonymous Users | The total number of users who established a non-anonymous connection with the FTP service (since service startup). If a client request for an anonymous connection is rejected and the client responds with valid authenticating data, the connection is counted as non-anonymous. |
Related topics: