使用Zabbix Api功能，跨互聯網監控Zabbix-Proxy狀態
作者：運維小弟
項目需要通過zabbix-proxy 來獲取監控數據【網絡是單向的，zabbix-proxy 通過公網主動連接 zabbix-server ，上報監控數據，已達到監控的目的】
背景：
項目需要通過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
- 獲取token：https://www.zabbix.com/documentation/4.0/zh/manual/api/reference/user/login
- 獲取proxy 代理信息： https://www.zabbix.com/documentation/4.0/zh/manual/api/reference/proxy/get
#獲取token：
- #入參：
- curl -s -X POST -H 'Content-Type: application/json' -d '
- {
- "jsonrpc": "2.0",
- "method": "user.login",
- "params": {
- "user": "Admin",
- "password": "PASSWORD"
- },
- "id": 1
- }' http://172.16.10.37:8888/api_jsonrpc.php;
- #回參：
- {"jsonrpc":"2.0","result":"為0qwewerwrsdfdsfdsafsd","id":1}
- #得到token 為0qwewerwrsdfdsfdsafsd
#獲取proxy 代理信息
- #利用上面獲取的token，來獲取api 中proxy 的代理信息
- #入參：
- curl -s -X POST -H 'Content-Type: application/json' -d '
- {
- "jsonrpc": "2.0",
- "method": "proxy.get",
- "params": {
- "output": "extend",
- "selectInterface": "extend"
- },
- "auth": "0qwewerwrsdfdsfdsafsd",
- "id": 1
- }' http://172.16.10.37:8888/api_jsonrpc.php
- #回參
- {
- "jsonrpc": "2.0",
- "result": [
- {
- "proxy_hostid": "0",
- "host": "a-proxy",
- "status": "5",
- "disable_until": "0",
- "error": "",
- "available": "0",
- "errors_from": "0",
- "lastaccess": "1637806905",
- "ipmi_authtype": "-1",
- "ipmi_privilege": "2",
- "ipmi_username": "",
- "ipmi_password": "",
- "ipmi_disable_until": "0",
- "ipmi_available": "0",
- "snmp_disable_until": "0",
- "snmp_available": "0",
- "maintenanceid": "0",
- "maintenance_status": "0",
- "maintenance_type": "0",
- "maintenance_from": "0",
- "ipmi_errors_from": "0",
- "snmp_errors_from": "0",
- "ipmi_error": "",
- "snmp_error": "",
- "jmx_disable_until": "0",
- "jmx_available": "0",
- "jmx_errors_from": "0",
- "jmx_error": "",
- "name": "",
- "flags": "0",
- "templateid": "0",
- "description": "a-proxy",
- "tls_connect": "1",
- "tls_accept": "1",
- "tls_issuer": "",
- "tls_subject": "",
- "tls_psk_identity": "",
- "tls_psk": "",
- "proxy_address": "1.1.1.1",
- "auto_compress": "1",
- "discover": "0",
- "proxyid": "10385",
- "interface": []
- },
- {
- "proxy_hostid": "0",
- "host": "b-proxy",
- "status": "5",
- "disable_until": "0",
- "error": "",
- "available": "0",
- "errors_from": "0",
- "lastaccess": "1637806906",
- "ipmi_authtype": "-1",
- "ipmi_privilege": "2",
- "ipmi_username": "",
- "ipmi_password": "",
- "ipmi_disable_until": "0",
- "ipmi_available": "0",
- "snmp_disable_until": "0",
- "snmp_available": "0",
- "maintenanceid": "0",
- "maintenance_status": "0",
- "maintenance_type": "0",
- "maintenance_from": "0",
- "ipmi_errors_from": "0",
- "snmp_errors_from": "0",
- "ipmi_error": "",
- "snmp_error": "",
- "jmx_disable_until": "0",
- "jmx_available": "0",
- "jmx_errors_from": "0",
- "jmx_error": "",
- "name": "",
- "flags": "0",
- "templateid": "0",
- "description": "b-proxy",
- "tls_connect": "1",
- "tls_accept": "1",
- "tls_issuer": "",
- "tls_subject": "",
- "tls_psk_identity": "",
- "tls_psk": "",
- "proxy_address": "1.1.1.1",
- "auto_compress": "1",
- "discover": "0",
- "proxyid": "10402",
- "interface": []
- },
- {
- "proxy_hostid": "0",
- "host": "c_proxy",
- "status": "5",
- "disable_until": "0",
- "error": "",
- "available": "0",
- "errors_from": "0",
- "lastaccess": "1637806905",
- "ipmi_authtype": "-1",
- "ipmi_privilege": "2",
- "ipmi_username": "",
- "ipmi_password": "",
- "ipmi_disable_until": "0",
- "ipmi_available": "0",
- "snmp_disable_until": "0",
- "snmp_available": "0",
- "maintenanceid": "0",
- "maintenance_status": "0",
- "maintenance_type": "0",
- "maintenance_from": "0",
- "ipmi_errors_from": "0",
- "snmp_errors_from": "0",
- "ipmi_error": "",
- "snmp_error": "",
- "jmx_disable_until": "0",
- "jmx_available": "0",
- "jmx_errors_from": "0",
- "jmx_error": "",
- "name": "",
- "flags": "0",
- "templateid": "0",
- "description": "c_proxy",
- "tls_connect": "1",
- "tls_accept": "1",
- "tls_issuer": "",
- "tls_subject": "",
- "tls_psk_identity": "",
- "tls_psk": "",
- "proxy_address": "1.1.1.1",
- "auto_compress": "1",
- "discover": "0",
- "proxyid": "10445",
- "interface": []
- }
- ],
- "id": 1
- }
再次過濾，找到lastaccess字段，該字段的值表示 proxy 當前的 時間戳，每5秒 內會發生變化;通過對比該字段的值 和 zabbix-server 當前時間戳的 時間差，來判斷 proxy 的狀態是否正常
添加監控項：
獲取 lastaccess字段 的值
創建監控腳本：
- [root@sre ~]# cd /etc/zabbix/zabbix_agentd.d
- [root@sre zabbix_agentd.d]# vim a-proxy-check.sh
- #!/bin/bash
- curl -s -X POST -H 'Content-Type: application/json' -d '
- {
- "jsonrpc": "2.0",
- "method": "proxy.get",
- "params": {
- "output": "extend",
- "selectInterface": "extend"
- },
- "auth": "0qwewerwrsdfdsfdsafsd",
- "id": 1
- }' http://172.16.10.37:8888/api_jsonrpc.php | awk -F '{"' '{print $3}' | awk -F ',' '{print $8}' | awk -F '"' '{print $4}'
- [root@sre zabbix_agentd.d]# chmod +x /etc/zabbix/zabbix_agentd.d/a-proxy-check.sh
修改 zabbix_agentd.conf 配置文件，創建KEY ，指定腳本路徑
- [root@sre ~]# vim /etc/zabbix/zabbix_agentd.conf
- ........
- UnsafeUserParameters=1
- #自定義一個key,監控a_proxy的狀態
- UserParameter=a_proxy_status,/bin/bash /etc/zabbix/zabbix_agentd.d/a-proxy-check.sh
- ........
重啟 zabbix-agent
- systemctl restart zabbix-agent
登錄到zabbix-server 使用zabbix-get 測試監控項
- [root@sre zabbix]# zabbix_get -s 172.16.10.37 -p 10050 -k "a_proxy_status"
- 1637923240
登錄到zabbix web 控制臺，
#添加監控項
#添加觸發器
觸發器表達式表示： 當a-proxy 時間戳的 值 和 zabbix 當前時間戳的值 ，相差60 秒 ，觸發告警
修改觸發器值，模擬觸發告警
總結： 本篇文能寫出來也是被逼無奈，單向網絡，跨互聯網監控，也是生產上一個案例吧.
責任編輯：姜華
來源：
今日頭條
