Indicate for each statistic which types may have a value for
that statistic.
Explain some of the provided statistics a little more deeply.
---
doc/configuration.txt | 129 ++++++++++++++++++++++++++++++++++----------------
1 file changed, 88 insertions(+), 41 deletions(-)
Hi,
This time with improved formatting, and "pxname" fixed.
Thanks,
James
diff --git a/doc/configuration.txt b/doc/configuration.txt
index 670dfee..5f1e300 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -12926,45 +12926,89 @@ Unix socket.
---------------
The statistics may be consulted either from the unix socket or from the HTTP
-page. Both means provide a CSV format whose fields follow.
-
- 0. pxname: proxy name
- 1. svname: service name (FRONTEND for frontend, BACKEND for backend, any name
- for server)
- 2. qcur: current queued requests
- 3. qmax: max queued requests
- 4. scur: current sessions
- 5. smax: max sessions
- 6. slim: sessions limit
- 7. stot: total sessions
- 8. bin: bytes in
- 9. bout: bytes out
- 10. dreq: denied requests
- 11. dresp: denied responses
- 12. ereq: request errors
- 13. econ: connection errors
- 14. eresp: response errors (among which srv_abrt)
- 15. wretr: retries (warning)
- 16. wredis: redispatches (warning)
+page. Both means provide a CSV format whose fields follow. In brackets after
+each field are the types for which the field may take a value. Types not
+in that list will always have a blank value for that field.
+
+ 0. pxname: proxy name [FRONTEND, BACKEND, SERVER]
+ 1. svname: service name (FRONTEND for frontend, BACKEND for backend, any
+ name for server) [FRONTEND, BACKEND, SERVER]
+ 2. qcur: current queued requests. For the backend this reports the number
+ queued without a server assigned. [BACKEND, SERVER]
+ 3. qmax: max value of qcur [BACKEND, SERVER]
+ 4. scur: current sessions [FRONTEND, BACKEND, SERVER]
+ 5. smax: max sessions [FRONTEND, BACKEND, SERVER]
+ 6. slim: configured session limit [FRONTEND, BACKEND, SERVER]
+ 7. stot: cumulative number of connections [FRONTEND, BACKEND, SERVER]
+ 8. bin: bytes in [FRONTED, BACKEND, SERVER]
+ 9. bout: bytes out [FRONTEND, BACKEND, SERVER]
+ 10. dreq: requests denied because of security concerns.
+ - For tcp this is because of a matched tcp-request content rule.
+ - For http this is because of a matched http-request or tarpit rule.
+ [FRONTEND, BACKEND]
+ 11. dresp: responses denied because of security concerns.
+ - For http this is because of a matched http-request rule, or
+ "option checkcache".
+ [FRONTEND, BACKEND, SERVER]
+ 12. ereq: request errors. Some of the possible causes are:
+ - early termination from the client, before the request has been sent.
+ - read error from the client
+ - client timeout
+ - client closed connection
+ - various bad requests from the client.
+ - request was tarpitted.
+ [FRONTEND]
+ 13. econ: number of requests that encountered an error trying to connect to
+ a backend server. The backend stat is the sum of the stat for all servers
+ of that backend, plus any connection errors not associated with a
+ particular server (such as the backend having no active servers).
+ [BACKEND, SERVER]
+ 14. eresp: response errors. srv_abrt will be counted here also. Some other
+ errors are:
+ - write error on the client socket (won't be counted for the server stat)
+ - failure applying filters to the response.
+ [BACKEND, SERVER]
+ 15. wretr: number of times a connection to a server was retried.
+ [BACKEND, SERVER]
+ 16. wredis: number of times a request was redispatched to another server.
+ The server value counts the number of times that server was switched
+ away from. [BACKEND, SERVER]
17. status: status (UP/DOWN/NOLB/MAINT/MAINT(via)...)
- 18. weight: server weight (server), total weight (backend)
+ [FRONTEND, BACKEND, SERVER]
+ 18. weight: server weight (server), total weight (backend) [BACKEND, SERVER]
19. act: server is active (server), number of active servers (backend)
+ [BACKEND, SERVER]
20. bck: server is backup (server), number of backup servers (backend)
- 21. chkfail: number of failed checks
- 22. chkdown: number of UP->DOWN transitions
- 23. lastchg: last status change (in seconds)
- 24. downtime: total downtime (in seconds)
- 25. qlimit: queue limit
+ [BACKEND, SERVER]
+ 21. chkfail: number of failed checks. (Only counts checks failed when the
+ server is up.) [SERVER]
+ 22. chkdown: number of UP->DOWN transitions. The backend counter counts
+ transitions to the whole backend being down, rather than the sum of the
+ counters for each server. [BACKEND, SERVER]
+ 23. lastchg: number of seconds since the last UP<->DOWN transition
+ [BACKEND, SERVER]
+ 24. downtime: total downtime (in seconds). The value for the backend is the
+ downtime for the whole backend, not the sum of the server downtime.
+ [BACKEND, SERVER]
+ 25. qlimit: configured maxqueue for the server, or nothing in the value is 0
+ (default, meaning no limit) [SERVER]
26. pid: process id (0 for first instance, 1 for second, ...)
- 27. iid: unique proxy id
- 28. sid: service id (unique inside a proxy)
- 29. throttle: warm up status
- 30. lbtot: total number of times a server was selected
- 31. tracked: id of proxy/server if tracking is enabled
+ [FRONTEND, BACKEND, SERVER]
+ 27. iid: unique proxy id [FRONTEND, BACKEND, SERVER]
+ 28. sid: server id (unique inside a proxy) [SERVER]
+ 29. throttle: current throttle percentage for the server, when slowstart is
+ active, or no value if not in slowstart. [SERVER]
+ 30. lbtot: total number of times a server was selected, either for new
+ sessions, or when re-dispatching. The server counter is the number
+ of times that server was selected. [BACKEND, SERVER]
+ 31. tracked: id of proxy/server if tracking is enabled. [SERVER]
32. type (0=frontend, 1=backend, 2=server, 3=socket)
+ [FRONTEND, BACKEND, SERVER]
33. rate: number of sessions per second over last elapsed second
- 34. rate_lim: limit on new sessions per second
+ [FRONTEND, BACKEND, SERVER]
+ 34. rate_lim: configured limit on new sessions per second [FRONTEND]
35. rate_max: max number of new sessions per second
+ [FRONTEND, BACKEND, SERVER]
36. check_status: status of last health check, one of:
UNK -> unknown
INI -> initializing
@@ -12982,20 +13026,23 @@ page. Both means provide a CSV format whose fields
follow.
L7TOUT -> layer 7 (HTTP/SMTP) timeout
L7RSP -> layer 7 invalid response - protocol error
L7STS -> layer 7 response error, for example HTTP 5xx
- 37. check_code: layer5-7 code, if available
- 38. check_duration: time in ms took to finish last health check
- 39. hrsp_1xx: http responses with 1xx code
- 40. hrsp_2xx: http responses with 2xx code
- 41. hrsp_3xx: http responses with 3xx code
- 42. hrsp_4xx: http responses with 4xx code
- 43. hrsp_5xx: http responses with 5xx code
+ [SERVER]
+ 37. check_code: layer5-7 code, if available [SERVER]
+ 38. check_duration: time in ms took to finish last health check [SERVER]
+ 39. hrsp_1xx: http responses with 1xx code [FRONTEND, BACKEND, SERVER]
+ 40. hrsp_2xx: http responses with 2xx code [FRONTEND, BACKEND, SERVER]
+ 41. hrsp_3xx: http responses with 3xx code [FRONTEND, BACKEND, SERVER]
+ 42. hrsp_4xx: http responses with 4xx code [FRONTEND, BACKEND, SERVER]
+ 43. hrsp_5xx: http responses with 5xx code [FRONTEND, BACKEND, SERVER]
44. hrsp_other: http responses with other codes (protocol error)
- 45. hanafail: failed health checks details
+ [FRONTEND, BACKEND, SERVER]
+ 45. hanafail: failed health checks details [SERVER]
46. req_rate: HTTP requests per second over last elapsed second
47. req_rate_max: max number of HTTP requests per second observed
48. req_tot: total number of HTTP requests received
- 49. cli_abrt: number of data transfers aborted by the client
+ 49. cli_abrt: number of data transfers aborted by the client [BACKEND, SERVER]
50. srv_abrt: number of data transfers aborted by the server (inc. in eresp)
+ [BACKEND, SERVER]
51. comp_in: number of HTTP response bytes fed to the compressor
52. comp_out: number of HTTP response bytes emitted by the compressor
53. comp_byp: number of bytes that bypassed the HTTP compressor (CPU/BW limit)
--
1.9.1
