Zabbix monitoring scripts for Yoda
The default method for deploying the monitoring scripts is the zabbix.yml
playbook in the main Yoda repository.
Use the zabbix_server parameter to configure the name of the Zabbix server, and
zabbix_version to configure the branch of the yoda-zabbix scripts repository to use.
The Zabbix agent uses a pre-shared key (PSK) to authenticate to the Zabbix server. This key, along with its identity (i.e. its name) is generated when the Ansible playbook runs. The PSK and its identity have to be retrieved from the Zabbix agent configuration file and configured on the Zabbix server manually.
For additional information about using pre-shared keys, please refer to:
https://www.zabbix.com/documentation/3.4/manual/encryption/using_pre_shared_keys
The monitoring scripts are currently organized by role.
A new item needs to be added to the user parameter file of its role: yoda_role.userparams.conf, where role should be one
of system, portal, irodscommon, icat or resource.
Example from yoda_icat.userparams.conf:
UserParameter=yoda.delayedrules.count,sudo /etc/zabbix/zabbix_agentd.d/monitorDelayedRules.sh
Use sudo if the zabbix agent requires sudo permissions to execute the command, and add the command to the yoda-zabbix-role-sudoers file
of the role.
Example:
zabbix ALL=NOPASSWD: /etc/zabbix/zabbix_agentd.d/monitorDelayedRules.sh
Ensure the yoda-zabbix-role-sudoers file has no syntax errors and has been tested. A syntax error can only be corrected with a re-install! Duplicate lines are not allowed.
See Change log.
This project is licensed under the GPLv3 license.
The full license can be found in LICENSE.