Monitor maxscale server with Zabbix server with zabbix http agent
This template monitors maxscale using zabbix http agent. Tested on zabbix server/proxy version 6.0.X and maxscale version > 2.5.X. The OS used was debian 11.
- {$MAXSCALE.HTTP.ADDRESS}: Mandatory. Maxscale`s rest-api listening ip. It can be a virtual ip if ucarp is used.
- {$MAXSCALE.HTTP.USER}: Optional. Defaults to admin.
- {$MAXSCALE.HTTP.PASSWORD}: Optional. Defaults to mariadb.
- {$MAXSCALE.HTTP.PORT}: Optional.Defaults to 8989.
- {$MAXSCALE.HTTP.SCHEMA}: Optional. Defaults to http://.
- Automatic discovery of maxscale backends.
- Automatic discovery of maxscale monitors.
- Automatic discovery of maxscale services.
- Automatic discovery of maxscale listeners.
- Automatic discovery of maxscale sessions.
- Trigger for maxscale version change and low uptime.
- Zabbix server/proxy must be initially configured with cURL (libcurl) support for http agent to work.
- Maxscale`s rest-api must be enabled
- Enable and configure maxscale`s http rest-api.
- Configure the firewall to allow zabbix server or proxy access the maxscale api if firewall is used
- Import the template on your zabbix server.
- Create a dummy host with zabbix agent interface as localhost for example. If you assign a proxy , the proxy will be issuing the http requests.
- Assign the maxscale-vip template to the dummy host.
- Configure template`s macros with custom values.