A saltstack formula to manage Zabbix.

This formula has been developed distributing declarations in different files to make it usable in most situations. It should be useful in scenarios ranging from a simple install of the packages (without any special configuration) to a more complex set-up with different nodes for agent, server, database and frontend.

First, see if providing pillar data is enough for your customization needs. That's the recommended way and should be enough for most cases. See that sometimes there's a key named extra_conf that's used to add arbitrary configuration lines in the templates provided.

When providing pillar data is not enough for your needs, you can apply the Template Override and Files Switch (TOFS) pattern as described in the documentation file TOFS_pattern.md.

The formula is designed to be independent from other formulas so you could use this in a non-100% salted environment (i.e. it's not required –although recommended– to use other formulas to provision other parts of a complete system).

If you want to use the EPEL repo packages, as the naming conventions are different, you need to tweak the default values of map.jinja to obtain the desired results. In short:

• Don't use the zabbix.agent.repo sls assuming that EPEL repos are already configured
• Override the map.jinja definitions using pillar values like this

zabbix:
  lookup:
    agent:
      pkg: zabbix22-agent
    server:
      pkg: zabbix22-server-mysql

Now you just have to use zabbix.agent.conf sls file and that's it.

Just as an example, this is a top.sls file to install a complete modular self-contained Zabbix system:

base:
  '*':
    - zabbix.agent.repo
    - zabbix.agent.conf

    - mysql.server.conf
    - mysql.client.conf
    - zabbix.mysql.conf
    - zabbix.mysql.schema

    - zabbix.server.repo
    - zabbix.server.conf

    - nginx.conf

    - php.fpm.repo
    - php.fpm.conf
    - php.fpm.mysql
    - php.fpm.bcmath
    - php.fpm.mbstring
    - php.fpm.gd
    - php.fpm.xml
    - php.fpm.opcache

    - zabbix.frontend.repo
    - zabbix.frontend.conf

You need the appropriate mysql, nginx and php formulas to complete the installation with this top.sls file.

Installs the zabbix-agent package and starts the associated zabbix- agent service.

Configures the zabbix-agent package.

Configures official Zabbix repo specifically for the agent. Actually it just includes zabbix.repo and adds a requisite for the pkg state declaration

Installs Zabbix frontend.

Configures the zabbix-frontend package. Actually you need to use other formulas for apache/nginx and php5-fpm to complete a working setup.

Configures official Zabbix repo specifically for the frontend. Actually it just includes zabbix.repo and adds a requisite for the pkg state declaration.

Creates database and mysql user for Zabbix.

Creates mysql schema for Zabbix.

Configures official Zabbix repo.

Installs the zabbix-server package and starts the associated zabbix- server service.

Configures the zabbix-server package.

Configures official Zabbix repo specifically for the server. Actually it just includes zabbix.repo and adds a requisite for the pkg state declaration

Declares users and groups that could be needed in other formulas (e.g. in the users formula to make an user pertain to the service group).