A SaltStack formula to manage Zabbix.
Table of Contents
- General notes
- Contributing to this repo
- Overview
- Available states
zabbix.agentzabbix.agent.confzabbix.agent.repozabbix.frontendzabbix.frontend.confzabbix.frontend.repozabbix.mysql.confzabbix.mysql.schemazabbix.pgsql.pkgszabbix.pgsql.confzabbix.pgsql.schemazabbix.proxyzabbix.proxy.confzabbix.proxy.repozabbix.repozabbix.serverzabbix.server.confzabbix.server.repozabbix.users
- Testing
See the full SaltStack Formulas installation and usage instructions.
If you are interested in writing or contributing to formulas, please pay attention to the Writing Formula Section.
If you want to use this formula, please pay attention to the FORMULA file and/or git tag,
which contains the currently released version. This formula is versioned according to Semantic Versioning.
See Formula Versioning Section for more details.
Commit message formatting is significant!!
Please see How to contribute for more details.
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.reposls assuming that EPEL repos are already configured - Override the
map.jinjadefinitions using pillar values like this
zabbix:
lookup:
agent:
pkg: zabbix22-agent
server:
pkg: zabbix22-server-mysqlNow 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.confYou need the appropriate mysql, nginx and php formulas to complete the
installation with this top.sls file.
If you are installing the zabbix agent for windows you will want to separate the
pillar for windows from other linux and unix agents
This is a pillar top.sls file example to separate windows and Ubuntu Zabbix agent
pillar files
base:
'os:Ubuntu':
- match: grain
- zabbix-agent-ubuntu
'os:Windows':
- match: grain
- zabbix-agent-windowsNote
See the full Salt Formulas doc.
zabbix.agentzabbix.agent.confzabbix.agent.repozabbix.frontendzabbix.frontend.confzabbix.frontend.repozabbix.mysql.confzabbix.mysql.schemazabbix.pgsql.pkgszabbix.pgsql.confzabbix.pgsql.schemazabbix.proxyzabbix.proxy.confzabbix.proxy.repozabbix.repozabbix.serverzabbix.server.confzabbix.server.repozabbix.users
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.
Install required psql packages.
Creates database and PostgreSQL user for Zabbix. Includes zabbix.pgsql.pkgs.
Creates PostgreSQL schema for Zabbix. Includes zabbix.pgsql.pkgs.
Installs the zabbix-proxy package and starts the associated zabbix-proxy service.
Configures the zabbix-proxy package.
Configures official Zabbix repo specifically for the proxy. Actually it just includes zabbix.repo and adds a requisite for the pkg state declaration
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).
Linux testing is done with kitchen-salt.
- Ruby
- Docker
$ gem install bundler
$ bundle install
$ bin/kitchen test [platform]Where [platform] is the platform name defined in kitchen.yml,
e.g. debian-9-2019-2-py3.
Creates the docker instance and runs the template main state, ready for testing.
Runs the inspec tests on the actual instance.
Removes the docker instance.
Runs all of the stages above in one go: i.e. destroy + converge + verify + destroy.
Gives you SSH access to the instance for manual testing.