如何使用ansible获取被控制机上的haproxy转发消息请求数
来源:互联网 发布:优酷显示网络请求出错 编辑:程序博客网 时间:2024/06/06 08:38
代码指令如下:
ansible $ansibleGroupName -m shell -a " echo 'show stat' | socat stdio /run/haproxy.sock |grep $haproxyGroupName|grep BACKEND|awk -F',' '{print \$31}'"
其中
这里有个坑 {print $31} 这个$需要转译
其他:haproxy中
echo ‘show stat’ | socat stdio /run/haproxy.sock指令获取各参数信息如下
# pxname,svname,qcur,qmax,scur,smax,slim,stot,bin,bout,dreq,dresp,ereq,econ,eresp,wretr,wredis,status,weight,act,bck,chkfail,chkdown,lastchg,downtime,qlimit,pid,iid,sid,throttle,lbtot,tracked,type,rate,rate_lim,rate_max,check_status,check_code,check_duration,hrsp_1xx,hrsp_2xx,hrsp_3xx,hrsp_4xx,hrsp_5xx,hrsp_other,hanafail,req_rate,req_rate_max,req_tot,cli_abrt,srv_abrt,comp_in,comp_out,comp_byp,comp_rsp,lastsess,last_chk,last_agt,qtime,ctime,rtime,ttime,SFY,FRONTEND,,,0,1,2000,5,305,2510,0,0,0,,,,,OPEN,,,,,,,,,1,2,0,,,,0,0,0,1,,,,,,,,,,,0,0,0,,,0,0,0,0,,,,,,,,SFY,-be0,0,0,0,1,,5,305,2510,,0,,0,0,0,0,UP,1,1,0,0,0,64999,344,,1,2,1,,5,,2,0,,1,L4OK,,0,,,,,,,0,,,,0,0,,,,,4276,,,0,0,0,11,SFY,-be1,0,0,0,0,,0,0,0,,0,,0,0,0,0,DOWN,1,1,0,1,1,72890,72890,,1,2,2,,0,,2,0,,0,L4CON,,0,,,,,,,0,,,,0,0,,,,,-1,Connection refused,,0,0,0,0,SFY,BACKEND,0,0,0,1,200,5,305,2510,0,0,,0,0,0,0,UP,1,1,0,,0,72891,0,,1,2,0,,5,,1,0,,1,,,,,,,,,,,,,,0,0,0,0,0,0,4276,,,0,0,0,11,stats_auth,FRONTEND,,,0,2,2000,67,71231,1197034,0,0,0,,,,,OPEN,,,,,,,,,1,3,0,,,,0,0,0,5,,,,0,64,1,2,64,0,,0,11,131,,,0,0,0,0,,,,,,,,stats_auth,BACKEND,0,0,0,1,200,64,71231,1197034,0,0,,64,0,0,0,UP,0,0,0,,0,72891,0,,1,3,0,,0,,1,0,,6,,,,0,0,0,0,64,0,,,,,0,0,0,0,0,0,4273,,,0,0,0,2,
含义如下
The statistics may be consulted either from the unix socket or from the HTTPpage. Both means provide a CSV format whose fields follow. The first linebegins with a sharp ('#') and has one word per comma-delimited field whichrepresents the title of the column. All other lines starting at the second oneuse a classical CSV format using a comma as the delimiter, and the double quote('"') as an optional text delimiter, but only if the enclosed text is ambiguous(if it contains a quote or a comma). The double-quote character ('"') in thetext is doubled ('""'), which is the format that most tools recognize. Pleasedo not insert any column before these ones in order not to break tools whichuse hard-coded column positions.In brackets after each field name are the types which may have a value forthat field. The types are L (Listeners), F (Frontends), B (Backends), andS (Servers). 0. pxname [LFBS]: proxy name 1. svname [LFBS]: service name (FRONTEND for frontend, BACKEND for backend, any name for server/listener) 2. qcur [..BS]: current queued requests. For the backend this reports the number queued without a server assigned. 3. qmax [..BS]: max value of qcur 4. scur [LFBS]: current sessions 5. smax [LFBS]: max sessions 6. slim [LFBS]: configured session limit 7. stot [LFBS]: cumulative number of connections 8. bin [LFBS]: bytes in 9. bout [LFBS]: bytes out 10. dreq [LFB.]: 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. 11. dresp [LFBS]: responses denied because of security concerns. - For http this is because of a matched http-request rule, or "option checkcache". 12. ereq [LF..]: 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. 13. econ [..BS]: 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). 14. eresp [..BS]: 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. 15. wretr [..BS]: number of times a connection to a server was retried. 16. wredis [..BS]: number of times a request was redispatched to another server. The server value counts the number of times that server was switched away from. 17. status [LFBS]: status (UP/DOWN/NOLB/MAINT/MAINT(via)...) 18. weight [..BS]: total weight (backend), server weight (server) 19. act [..BS]: number of active servers (backend), server is active (server) 20. bck [..BS]: number of backup servers (backend), server is backup (server) 21. chkfail [...S]: number of failed checks. (Only counts checks failed when the server is up.) 22. chkdown [..BS]: 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. 23. lastchg [..BS]: number of seconds since the last UP<->DOWN transition 24. downtime [..BS]: total downtime (in seconds). The value for the backend is the downtime for the whole backend, not the sum of the server downtime. 25. qlimit [...S]: configured maxqueue for the server, or nothing in the value is 0 (default, meaning no limit) 26. pid [LFBS]: process id (0 for first instance, 1 for second, ...) 27. iid [LFBS]: unique proxy id 28. sid [L..S]: server id (unique inside a proxy) 29. throttle [...S]: current throttle percentage for the server, when slowstart is active, or no value if not in slowstart. 30. lbtot [..BS]: 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. 31. tracked [...S]: id of proxy/server if tracking is enabled. 32. type [LFBS]: (0=frontend, 1=backend, 2=server, 3=socket/listener) 33. rate [.FBS]: number of sessions per second over last elapsed second 34. rate_lim [.F..]: configured limit on new sessions per second 35. rate_max [.FBS]: max number of new sessions per second 36. check_status [...S]: status of last health check, one of: UNK -> unknown INI -> initializing SOCKERR -> socket error L4OK -> check passed on layer 4, no upper layers testing enabled L4TOUT -> layer 1-4 timeout L4CON -> layer 1-4 connection problem, for example "Connection refused" (tcp rst) or "No route to host" (icmp) L6OK -> check passed on layer 6 L6TOUT -> layer 6 (SSL) timeout L6RSP -> layer 6 invalid response - protocol error L7OK -> check passed on layer 7 L7OKC -> check conditionally passed on layer 7, for example 404 with disable-on-404 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 [...S]: layer5-7 code, if available 38. check_duration [...S]: time in ms took to finish last health check 39. hrsp_1xx [.FBS]: http responses with 1xx code 40. hrsp_2xx [.FBS]: http responses with 2xx code 41. hrsp_3xx [.FBS]: http responses with 3xx code 42. hrsp_4xx [.FBS]: http responses with 4xx code 43. hrsp_5xx [.FBS]: http responses with 5xx code 44. hrsp_other [.FBS]: http responses with other codes (protocol error) 45. hanafail [...S]: failed health checks details 46. req_rate [.F..]: HTTP requests per second over last elapsed second 47. req_rate_max [.F..]: max number of HTTP requests per second observed 48. req_tot [.F..]: total number of HTTP requests received 49. cli_abrt [..BS]: number of data transfers aborted by the client 50. srv_abrt [..BS]: number of data transfers aborted by the server (inc. in eresp) 51. comp_in [.FB.]: number of HTTP response bytes fed to the compressor 52. comp_out [.FB.]: number of HTTP response bytes emitted by the compressor 53. comp_byp [.FB.]: number of bytes that bypassed the HTTP compressor (CPU/BW limit) 54. comp_rsp [.FB.]: number of HTTP responses that were compressed 55. lastsess [..BS]: number of seconds since last session assigned to server/backend 56. last_chk [...S]: last health check contents or textual error 57. last_agt [...S]: last agent check contents or textual error 58. qtime [..BS]: the average queue time in ms over the 1024 last requests 59. ctime [..BS]: the average connect time in ms over the 1024 last requests 60. rtime [..BS]: the average response time in ms over the 1024 last requests (0 for TCP) 61. ttime [..BS]: the average total session time in ms over the 1024 last requests
阅读全文
0 0
- 如何使用ansible获取被控制机上的haproxy转发消息请求数
- 使用Ansible向被控节点配置yum源
- 请求转发和重定向的区别?以及如何使用?
- 如何使用fiddler转发请求功能
- 如何使用charles代理转发请求
- 如何在javascript中获取请求转发后的request对象传递的数据
- 使用javascript方式获取多说评论插件的文章评论数,转发数
- 如何获取对hbase的请求rpc数
- 使用Fiddler的AutoResponder转发请求
- (10A)HttpServletRequest:获取客户机信息、获取消息头信息、获取客户机请求参数、请求转发forward
- 使用getNamedDispatcher()转发请求
- Ansible的使用
- ANSIBLE的简单使用
- 如何使用Ansible 2的API做python开发
- 如何使用Ansible 2的API做python开发
- servlet获取表单提交的数据、请求转发、请求包含、请求重定向
- OC的消息转发
- 请求转发的问题
- Git下载 Git
- bootstrap table--JS组件系列——表格组件神器
- Go与C语言的互操作
- 应对不同情况的多行文本溢出
- (UESTC
- 如何使用ansible获取被控制机上的haproxy转发消息请求数
- ffmpeg 双路输入解析——以vf_overlay为例
- LeetCode 48. Rotate Image
- leetcode 63. Unique Paths II DP动态规划
- contextmenu事件
- 给websocket加入心跳包防止自动断开连接
- Mybatis的动态sql
- 连续最大乘积
- 通过获取图片中的EXIF信息来定位拍摄地点