使用Zabbix Api功能，跨互联网监控Zabbix-Proxy状态

背景：

项目需要通过zabbix-proxy 来获取监控数据【网络是单向的，zabbix-proxy 通过公网主动连接 zabbix-server ，上报监控数据，已达到监控的目的】

需求：

因为是单向网络，proxy 挂了后，zabbix master 都无法获取到 zabbix-proxy 和 下面的agent 机器的离线的状态，更不会触发告警;现需要对 zabbix-proxy 的状态实行监控，利用 zabbix-proxy 主动上传到 zabbix 页面上的 agent 代理程序的 状态 来判断 zabbix-proxy 的存活

思路：

通过获取 zabbix api 中 Proxy 代理 的 信息 来实现 监控

官方api说明：

版本：zabbix4.0

1. 获取token：https://www.zabbix.com/documentation/4.0/zh/manual/api/reference/user/login
3. 获取proxy 代理信息： https://www.zabbix.com/documentation/4.0/zh/manual/api/reference/proxy/get

#获取token：

1. #入参：
2. curl -s -X POST -H 'Content-Type: application/json' -d '
3. {
4. "jsonrpc": "2.0",
5. "method": "user.login",
6. "params": {
7. "user": "Admin",
8. "password": "PASSWORD"
9. },
10. "id": 1
11. }' http://172.16.10.37:8888/api_jsonrpc.php;
13. #回参：
14. {"jsonrpc":"2.0","result":"为0qwewerwrsdfdsfdsafsd","id":1}
16. #得到token 为0qwewerwrsdfdsfdsafsd

#获取proxy 代理信息

1. #利用上面获取的token，来获取api 中proxy 的代理信息
3. #入参：
4. curl -s -X POST -H 'Content-Type: application/json' -d '
5. {
6. "jsonrpc": "2.0",
7. "method": "proxy.get",
8. "params": {
9. "output": "extend",
10. "selectInterface": "extend"
11. },
12. "auth": "0qwewerwrsdfdsfdsafsd",
13. "id": 1
14. }' http://172.16.10.37:8888/api_jsonrpc.php
17. #回参
18. {
19. "jsonrpc": "2.0",
20. "result": [
21. {
22. "proxy_hostid": "0",
23. "host": "a-proxy",
24. "status": "5",
25. "disable_until": "0",
26. "error": "",
27. "available": "0",
28. "errors_from": "0",
29. "lastaccess": "1637806905",
30. "ipmi_authtype": "-1",
31. "ipmi_privilege": "2",
32. "ipmi_username": "",
33. "ipmi_password": "",
34. "ipmi_disable_until": "0",
35. "ipmi_available": "0",
36. "snmp_disable_until": "0",
37. "snmp_available": "0",
38. "maintenanceid": "0",
39. "maintenance_status": "0",
40. "maintenance_type": "0",
41. "maintenance_from": "0",
42. "ipmi_errors_from": "0",
43. "snmp_errors_from": "0",
44. "ipmi_error": "",
45. "snmp_error": "",
46. "jmx_disable_until": "0",
47. "jmx_available": "0",
48. "jmx_errors_from": "0",
49. "jmx_error": "",
50. "name": "",
51. "flags": "0",
52. "templateid": "0",
53. "description": "a-proxy",
54. "tls_connect": "1",
55. "tls_accept": "1",
56. "tls_issuer": "",
57. "tls_subject": "",
58. "tls_psk_identity": "",
59. "tls_psk": "",
60. "proxy_address": "1.1.1.1",
61. "auto_compress": "1",
62. "discover": "0",
63. "proxyid": "10385",
64. "interface": []
65. },
66. {
67. "proxy_hostid": "0",
68. "host": "b-proxy",
69. "status": "5",
70. "disable_until": "0",
71. "error": "",
72. "available": "0",
73. "errors_from": "0",
74. "lastaccess": "1637806906",
75. "ipmi_authtype": "-1",
76. "ipmi_privilege": "2",
77. "ipmi_username": "",
78. "ipmi_password": "",
79. "ipmi_disable_until": "0",
80. "ipmi_available": "0",
81. "snmp_disable_until": "0",
82. "snmp_available": "0",
83. "maintenanceid": "0",
84. "maintenance_status": "0",
85. "maintenance_type": "0",
86. "maintenance_from": "0",
87. "ipmi_errors_from": "0",
88. "snmp_errors_from": "0",
89. "ipmi_error": "",
90. "snmp_error": "",
91. "jmx_disable_until": "0",
92. "jmx_available": "0",
93. "jmx_errors_from": "0",
94. "jmx_error": "",
95. "name": "",
96. "flags": "0",
97. "templateid": "0",
98. "description": "b-proxy",
99. "tls_connect": "1",
100. "tls_accept": "1",
101. "tls_issuer": "",
102. "tls_subject": "",
103. "tls_psk_identity": "",
104. "tls_psk": "",
105. "proxy_address": "1.1.1.1",
106. "auto_compress": "1",
107. "discover": "0",
108. "proxyid": "10402",
109. "interface": []
110. },
111. {
112. "proxy_hostid": "0",
113. "host": "c_proxy",
114. "status": "5",
115. "disable_until": "0",
116. "error": "",
117. "available": "0",
118. "errors_from": "0",
119. "lastaccess": "1637806905",
120. "ipmi_authtype": "-1",
121. "ipmi_privilege": "2",
122. "ipmi_username": "",
123. "ipmi_password": "",
124. "ipmi_disable_until": "0",
125. "ipmi_available": "0",
126. "snmp_disable_until": "0",
127. "snmp_available": "0",
128. "maintenanceid": "0",
129. "maintenance_status": "0",
130. "maintenance_type": "0",
131. "maintenance_from": "0",
132. "ipmi_errors_from": "0",
133. "snmp_errors_from": "0",
134. "ipmi_error": "",
135. "snmp_error": "",
136. "jmx_disable_until": "0",
137. "jmx_available": "0",
138. "jmx_errors_from": "0",
139. "jmx_error": "",
140. "name": "",
141. "flags": "0",
142. "templateid": "0",
143. "description": "c_proxy",
144. "tls_connect": "1",
145. "tls_accept": "1",
146. "tls_issuer": "",
147. "tls_subject": "",
148. "tls_psk_identity": "",
149. "tls_psk": "",
150. "proxy_address": "1.1.1.1",
151. "auto_compress": "1",
152. "discover": "0",
153. "proxyid": "10445",
154. "interface": []
155. }
156. ],
157. "id": 1
158. }

再次过滤，找到lastaccess字段，该字段的值表示 proxy 当前的 时间戳，每5秒 内会发生变化;通过对比该字段的值 和 zabbix-server 当前时间戳的 时间差，来判断 proxy 的状态是否正常

添加监控项：

获取 lastaccess字段 的值

创建监控脚本：

1. [root@sre ~]# cd /etc/zabbix/zabbix_agentd.d
3. [root@sre zabbix_agentd.d]# vim a-proxy-check.sh
4. #!/bin/bash
5. curl -s -X POST -H 'Content-Type: application/json' -d '
6. {
7. "jsonrpc": "2.0",
8. "method": "proxy.get",
9. "params": {
10. "output": "extend",
11. "selectInterface": "extend"
12. },
13. "auth": "0qwewerwrsdfdsfdsafsd",
14. "id": 1
15. }' http://172.16.10.37:8888/api_jsonrpc.php | awk -F '{"' '{print $3}' | awk -F ',' '{print $8}' | awk -F '"' '{print $4}'
18. [root@sre zabbix_agentd.d]# chmod +x /etc/zabbix/zabbix_agentd.d/a-proxy-check.sh

修改 zabbix_agentd.conf 配置文件，创建KEY ，指定脚本路径

1. [root@sre ~]# vim /etc/zabbix/zabbix_agentd.conf
2. ........
3. UnsafeUserParameters=1
4. #自定义一个key,监控a_proxy的状态
5. UserParameter=a_proxy_status,/bin/bash /etc/zabbix/zabbix_agentd.d/a-proxy-check.sh
6. ........

重启 zabbix-agent

1. systemctl restart zabbix-agent

登录到zabbix-server 使用zabbix-get 测试监控项

1. [root@sre zabbix]# zabbix_get -s 172.16.10.37 -p 10050 -k "a_proxy_status"
2. 1637923240

登录到zabbix web 控制台，

#添加监控项

#添加触发器

触发器表达式表示： 当a-proxy 时间戳的 值 和 zabbix 当前时间戳的值 ，相差60 秒 ，触发告警

修改触发器值，模拟触发告警

总结： 本篇文能写出来也是被逼无奈，单向网络，跨互联网监控，也是生产上一个案例吧.

原文链接：https://www.toutiao.com/a7034827437355614750/