Export (0) Print
Expand All

SOCKS filter performance counters

Updated: February 1, 2011

Applies To: Forefront Threat Management Gateway (TMG)

The following table lists the performance counters for the SOCKS filter.

 

Performance counter Description

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).

Active Sessions

A single SOCKS session includes the CONNECT and BIND commands for a single client.

Bytes Read/sec

The number of bytes read on all SOCKS connections per second. The term bytes read refers to the amount of data sent 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.

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).

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.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft