Table of Contents
- Overview
- Upgrades
- Requirements
- Installation
- Role Variables
- Dependencies
- Example Playbook
- Molecule
- Contributors
- License
- Author Information
Badges:
This is a role for installing and maintaining the zabbix-server.
This is one of the 'dj-wasabi' roles which configures your whole zabbix environment. See below for the complete list:
- zabbix-web (https://galaxy.ansible.com/dj-wasabi/zabbix-web/)
- zabbix-server (https://galaxy.ansible.com/dj-wasabi/zabbix-server/)
- zabbix-proxy (https://galaxy.ansible.com/dj-wasabi/zabbix-proxy/)
- zabbix-javagateway (https://galaxy.ansible.com/dj-wasabi/zabbix-javagateway/)
- zabbix-agent (https://galaxy.ansible.com/dj-wasabi/zabbix-agent/)
With this 1.0.0 release, the following is changed:
- This repository will only contain all the actions that are needed for correctly configuring a Zabbix Server. All tasks regarding the frontend/webui of Zabbix has been transferred to the
dj-wasabi.zabbix-web
role. - All properties start with
zabbix_
now. Example, property namedserver_dbuser
is nowzabbix_server_dbuser
.
This role will work on the following operating systems:
- Red Hat
- Debian
- Ubuntu
So, you'll need one of those operating systems.. :-) Please send Pull Requests or suggestions when you want to use this role for other Operating systems.
See the following list of supported Operating systems with the Zabbix releases:
- CentOS 7.x, 8.x
- Amazon 7.x
- RedHat 7.x, 8.x
- OracleLinux 7.x, 8.x
- Scientific Linux 7.x, 8.x
- Ubuntu 14.04, 16.04, 18.04
- Debian 8, 9
- CentOS 7.x
- Amazon 7.x
- RedHat 7.x
- OracleLinux 7.x
- Scientific Linux 7.x
- Ubuntu 14.04, 16.04, 18.04
- Debian 8, 9
- CentOS 7.x
- Amazon 7.x
- RedHat 7.x
- OracleLinux 7.x
- Scientific Linux 7.x
- Ubuntu 14.04, 16.04, 18.04
- Debian 8, 9
- CentOS 7.x
- Amazon 7.x
- RedHat 7.x
- OracleLinux 7.x
- Scientific Linux 7.x
- Ubuntu 14.04, 16.04
- Debian 7, 8, 9
- CentOS 7.x
- Amazon 7.x
- RedHat 7.x
- OracleLinux 7.x
- Scientific Linux 7.x
- Ubuntu 14.04, 16.04
- Debian 7, 8
- CentOS 5.x, 6.x, 7.x
- Amazon 5.x, 6.x, 7.x
- RedHat 5.x, 6.x, 7.x
- OracleLinux 5.x, 6.x, 7.x
- Scientific Linux 5.x, 6.x, 7.x
- Ubuntu 14.04
- Debian 7, 8
- CentOS 6.x, 7.x
- Amazon 6.x, 7.x
- RedHat 6.x, 7.x
- OracleLinux 6.x, 7.x
- Scientific Linux 6.x, 7.x
- Ubuntu 12.04 14.04
- Debian 7
- CentOS 5.x, 6.x
- RedHat 5.x, 6.x
- OracleLinux 5.x, 6.x
- Scientific Linux 5.x, 6.x
- Ubuntu 12.04
- Debian 7
- xenserver 6
Installing this role is very simple: ansible-galaxy install dj-wasabi.zabbix-server
Please be aware that this role only installs the Zabbix Server and not the Zabbix Web. If you do want to have a Zabbix Web, please execute the following command: ansible-galaxy install dj-wasabi.zabbix-web
Default username/password for the Zabbix Web interface is the default one installed by Zabbix.
Username: Admin Password: zabbix
The following is an overview of all available configuration default for this role.
zabbix_server_version
: This is the version of zabbix. Default: 4.4. Can be overridden to 3.2, 3.0, 2.4, or 2.2. Previously the variablezabbix_version
was used directly but it could cause some inconvenience. That variable is maintained by retrocompativility.zabbix_repo_yum
: A list with Yum repository configuration.zabbix_repo
: Default: zabbix- epel install agent from EPEL repo
- zabbix (default) install agent from Zabbix repo
- other install agent from pre-existing or other repo
zabbix_server_package_state
: Default: present. Can be overridden to "latest" to update packages when needed.zabbix_service_state
: Default:started
. Can be overridden to stopped if neededzabbix_service_enabled
: Default:True
Can be overridden toFalse
if neededzabbix_selinux
: Enables an SELinux policy so that the server will run. Default: False.
zabbix_server_name
: The name of the Zabbix Server.zabbix_server_database
: The type of database used. Can be: mysql or pgsqlzabbix_server_database_long
: The type of database used, but long name. Can be: mysql or postgresqlzabbix_server_hostname
: The hostname on which the zabbix-server is running. Default set to: {{ inventory_hostname }}zabbix_server_listenport
: On which port the Zabbix Server is available. Default: 10051zabbix_server_dbhost
: The hostname on which the database is running.zabbix_server_real_dbhost
: The hostname of the dbhost that is running behind a loadbalancer/VIP (loadbalancers doesn't accept ssh connections)zabbix_server_dbname
: The database name which is used by the Zabbix Server.zabbix_server_dbuser
: The database username which is used by the Zabbix Server.zabbix_server_dbpassword
: The database user password which is used by the Zabbix Server.zabbix_server_dbport
: The database port which is used by the Zabbix Server.zabbix_database_creation
: True / False. When you don't want to create the database including user, you can set it to False.zabbix_server_install_recommends
: True / False. False does not install the recommended packages that come with the zabbix-server install. Default truezabbix_server_install_database_client
: True / False. False does not install database client. Default truezabbix_database_sqlload
:True / False. When you don't want to load the sql files into the database, you can set it to False.zabbix_server_dbencoding
: The encoding for the MySQL database. Default set toutf8
zabbix_server_dbcollation
: The collation for the MySQL database. Default set toutf8_bin
zabbix_server_manage_service
: True / False. When you run multiple Zabbix servers in a High Available cluster setup (e.g. pacemaker), you don't want Ansible to manage the zabbix-server service, because Pacemaker is in control of zabbix-server service.
Define these variables to copy scripts to your respective scripts path.
zabbix_server_alertscripts
: List of alertscripts to be added tozabbix_server_alertscriptspath
zabbix_server_externalscripts
: List of alertscripts to be added tozabbix_server_externalscriptspath
Example:
zabbix_server_alertscripts:
- path: "{{ lookup('first_found', 'zabbix-scripts/somescript.php') }}"
name: "somescript.php"
These variables are specific for Zabbix 3.0 and higher:
zabbix_server_tlsconnect
: How the agent should connect to server or proxy. Used for active checks. Possible values:- unencrypted
- psk
- cert
zabbix_server_tlsaccept
: What incoming connections to accept. Possible values:- unencrypted
- psk
- cert
zabbix_server_tlscafile
: Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification.zabbix_server_tlscrlfile
: Full pathname of a file containing revoked certificates.zabbix_server_tlsservercertissuer
: Allowed server certificate issuer.zabbix_server_tlsservercertsubject
: Allowed server certificate subject.zabbix_server_tlscertfile
: Full pathname of a file containing the agent certificate or certificate chain.zabbix_server_tlskeyfile
: Full pathname of a file containing the agent private key.
There are some zabbix-server specific variables which will be used for the zabbix-server configuration file. These can be found in the defaults/main.yml file. There are 3 which need some explanation:
#zabbix_server_database: mysql
#zabbix_server_database_long: mysql
zabbix_server_database: pgsql
zabbix_server_database_long: postgresql
[...]
zabbix_server_dbport: 5432
There are 2 database_types which will be supported: mysql and postgresql. You'll need to comment or uncomment the database you would like to use and adjust the port number (server_dbport
) accordingly (5432
is the default postgresql port). In example from above, the postgresql database is used. If you want to use mysql, uncomment the 2 lines from mysql and comment the 2 lines for postgresql and change the database port to the mysql one (default mysql port is 3306
).
If you use mysql, then you should define mysql username, password and host to prepare zabbix database, otherwise they will be considered as their default value (and therefore, connecting to database will be considered as connecting to localhost with no password). The keys are below:
zabbix_server_mysql_login_host
zabbix_server_mysql_login_user
zabbix_server_mysql_login_password
If you use pgsql, then you should define pgsql username, password and host to prepare zabbix database, otherwise they will be considered as their default value (and therefore, connecting to database will be considered as connecting to localhost with no password). The keys are below:
zabbix_server_pgsql_login_host
zabbix_server_pgsql_login_user
zabbix_server_pgsql_login_password
For the databases you should find a role that suits your needs, as I don't want to force you for using a specific role. Before applying this Zabbix Server role, the database service should already be installed and running, and should be able to handle the modules in Ansible that belong to that database.
This role will not install a MySQL or PostgreSQL service.
This role will create a Zabbix user and a Zabbix database in the configured database type.
Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:
- hosts: zabbix-server
become: yes
roles:
- { role: dj-wasabi.zabbix-server, zabbix_server_database: mysql, zabbix_server_database_long: mysql }
This role is configured to be tested with Molecule. You can find on these pages some more information regarding Molecule:
- http://werner-dijkerman.nl/2016/07/10/testing-ansible-roles-with-molecule-testinfra-and-docker/
- http://werner-dijkerman.nl/2016/07/27/extending-ansible-role-testing-with-molecule-by-adding-group_vars-dependencies-and-using-travis-ci/
- http://werner-dijkerman.nl/2016/07/31/testing-ansible-roles-in-a-cluster-setup-with-docker-and-molecule/
The following have contributed to this Ansible role (List of Fame):
- drmikecrowe
- srvg
- kostyrevaa
- clopnis
- SAL-e
- lhoss
- mescanef
MIT
This is my first attempt to create an ansible role, so please send suggestion or pull requests to make this role better.
Github: https://github.com/dj-wasabi/ansible-zabbix-server
mail: ikben [ at ] werner-dijkerman . nl