Statistics

Server or backend status:

Elapsed time since the last status change

Health check failures counter

DOWN status counter

DOWN status elapsed time

Proportion of traffic this server is configured to accept, based on the weight parameter. The backend row shows the number of connected servers versus total servers.

Indicates whether server is functioning as an active server (Yes) or a backup server (No). The backend row shows the number of connected active servers versus total active servers.

Indicates whether server is functioning as a backup server (Yes) or an active server (No). The backend row shows the number of connected backup servers versus total backup servers.

Number of concurrent connections/sessions

Highest number of connections/sessions that have ever been established simultaneously

Maximum number of simultaneous connections/sessions allowed as determined by the maxconn setting on each server line or, for the backend row, either the value of fullconn or the total of the limit values of the frontends that route to this backend divided by 10. For example, if two frontends route to this backend, and the total of their limit values is 4000, the connection limit is 400.

Cumulative number of connections

The total number of times the given server was selected to serve a request. This can be due to normal load balancing or because of a redispatch from a failed server. The backend row shows the total for all servers in the backend.

Number of client connections waiting to be assigned to a server

Highest number of clients that have ever been queued simultaneously

Maximum number of connections that are allowed to be queued, as defined by the maxqueue setting on each server line

Number of requests deemed security threats and rejected using one of the following directives:

• http-request deny

• http-request reject

• http-request silent-drop

• http-request tarpit

• http-response silent-drop

• tcp-request content reject

• tcp-request content silent-drop

• tcp-response content silent-drop

Number of requests deemed security threats and rejected using the http-response deny or tcp-response content reject directive.

Not used

Number of requests that encountered an error while trying to connect to the server

Number of errors encountered while getting the response.

Connection retry counter (when backend configured with retries)

Number of redispatched connections (when backend configured with option redispatch)

Rate at which connections are being made to a server

Highest rate at which connections have ever been established to the given server

HTTP 1xx, 2xx, and 3xx code counter. Hover over the value to see the breakdown for each class of codes.

HTTP 4xx, 5xx, and other code counter. Hover over the value to see the breakdown for each class of codes.

Non-HTTP error counter

Number of times a client disconnects in DATA phase

Number of times a server disconnects in DATA phase

The amount of data sent by the load balancer to the upstream server. The backend row shows the total for all servers.

The amount of data received by the load balancer from the upstream server. The backend row shows the total for all servers.

Frontend status. When OPEN, the frontend is operating normally and ready to receive traffic. When you disable the frontend, the status becomes STOP.

Number of concurrent fully established connections/sessions

Highest number of fully-established connections/sessions that have ever been in use simultaneously

Maximum number of simultaneous fully-established connections/sessions allowed

Cumulative number of fully established connections

Number of requests deemed security threats and rejected using one of the following directives:

• http-request deny

• http-request reject

• http-request silent-drop

• http-request tarpit

• http-response silent-drop

• tcp-request connection silent-drop

• tcp-request content reject

• tcp-request content silent-drop

Number of requests deemed security threats and rejected using the http-response deny directive.

The number of requests that have encountered an error. Possible causes include:

• early termination from the client

• a read error from the client

• the client timed out

• the client closed the connection

• the client sent a malformed request

• the request was tar pitted

The rate at which clients are connecting to the load balancer (not yet fully established as sessions)

The highest number of non-fully-established connections that have ever been in use simultaneously

Maximum number of non-complfully-establishedeted connections per second allowed

Rate at which HTTP requests are being received over established connections

Highest rate at which HTTP requests have been received over established connections

HTTP 1xx, 2xx, and 3xx code counter. Hover over the value to see the breakdown for each class of codes.

HTTP 4xx, 5xx, and other code counter. Hover over the value to see the breakdown for each class of codes.

Cumulative amount of data received by load balancer from downstream clients

Cumulative amount of data sent by load balancer to downstream clients