What is Zabbix?
Zabbix is an enterprise-class open source distributed monitoring solution.
Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.
What is Zabbix server?
Zabbix server is the central process of Zabbix software.
The server performs the polling and trapping of data, it calculates triggers, sends notifications to users. It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems. The server can itself remotely check networked services (such as web servers and mail servers) using simple service checks.
Zabbix server images
These are the only official Zabbix server Docker images. They are based on latest Alpine and trusty Ubuntu images. The available versions of Zabbix server are:
Zabbix server 3.0 (tags: alpine-3.0-latest, ubuntu-3.0-latest) Zabbix server 3.0.* (tags: alpine-3.0.*, ubuntu-3.0.*) Zabbix server 3.2 (tags: alpine-3.2-latest, ubuntu-3.2-latest, alpine-latest, ubuntu-latest, latest) Zabbix server 3.2.* (tags: alpine-3.2.*, ubuntu-3.2.*) Zabbix server 3.4 (tags: alpine-trunk, ubuntu-trunk)
Images are updated when new releases are published. The image with
latest tag is based on Alpine Linux.
The image uses PostgreSQL database. It uses the next procedure to start:
- Checking database availability
- Checking of having
POSTGRES_DBdatabase name if it does not exist
- Checking of having
dbversiontable. Creating Zabbix server database schema and upload initial data sample if no
How to use this image
Start a Zabbix server container as follows:
docker run --name some-zabbix-server-pgsql -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER="some-user" -e POSTGRES_PASSWORD="some-password" -d zabbix/zabbix-server-pgsql:tag
some-zabbix-server-pgsql is the name you want to assign to your container,
some-postgres-server is IP or DNS name of PostgreSQL server,
some-user is user to connect to Zabbix database on PostgreSQL server,
some-password is the password to connect to PostgreSQL server and
tag is the tag specifying the version you want. See the list above for relevant tags, or look at the full list of tags.
Container shell access and viewing Zabbix server logs
docker exec command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your
$ docker exec -ti some-zabbix-server-pgsql /bin/bash
The Zabbix server log is available through Docker's container log:
$ docker logs some-zabbix-server-pgsql
When you start the
zabbix-server-pgsql image, you can adjust the configuration of the Zabbix server by passing one or more environment variables on the
docker run command line.
This variable is IP or DNS name of PostgreSQL server. By default, value is 'postgres-server'
This variable is port of PostgreSQL server. By default, value is '5432'.
These variables are used by Zabbix server to connect to Zabbix database. By default, values are
The variable is Zabbix database name. By default, value is
The variable is list of comma separated loadable Zabbix modules. It works with volume
/var/lib/zabbix/modules. The syntax of the variable is
The variable is used to specify debug level. By default, value is
3. It is
DebugLevel parameter in
zabbix_server.conf. Allowed values are listed below:
0- basic information about starting and stopping of Zabbix processes;
1- critical information
2- error information
4- for debugging (produces lots of information)
5- extended debugging (produces even more information)
The variable is used to specify timeout for processing checks. By default, value is
The variable enable communication with Zabbix Java Gateway to collect Java related checks. By default, value is
Additionally the image allows to specify many other environment variables listed below:
ZBX_STARTPOLLERS=5 ZBX_IPMIPOLLERS=0 ZBX_STARTPOLLERSUNREACHABLE=1 ZBX_STARTTRAPPERS=5 ZBX_STARTPINGERS=1 ZBX_STARTDISCOVERERS=1 ZBX_STARTHTTPPOLLERS=1 ZBX_STARTTIMERS=1 ZBX_STARTESCALATORS=1 ZBX_JAVAGATEWAY=zabbix-java-gateway ZBX_JAVAGATEWAYPORT=10052 ZBX_STARTJAVAPOLLERS=5 ZBX_STARTVMWARECOLLECTORS=0 ZBX_VMWAREFREQUENCY=60 ZBX_VMWAREPERFFREQUENCY=60 ZBX_VMWARECACHESIZE=8M ZBX_VMWARETIMEOUT=10 ZBX_ENABLE_SNMP_TRAPS=false ZBX_HOUSEKEEPINGFREQUENCY=1 ZBX_MAXHOUSEKEEPERDELETE=5000 ZBX_SENDERFREQUENCY=30 ZBX_CACHESIZE=8M ZBX_CACHEUPDATEFREQUENCY=60 ZBX_STARTDBSYNCERS=4 ZBX_HISTORYCACHESIZE=16M ZBX_HISTORYINDEXCACHESIZE=4M ZBX_TRENDCACHESIZE=4M ZBX_VALUECACHESIZE=8M ZBX_TRAPPERIMEOUT=300 ZBX_UNREACHABLEPERIOD=45 ZBX_UNAVAILABLEDELAY=60 ZBX_UNREACHABLEDELAY=15 ZBX_LOGSLOWQUERIES=3000 ZBX_STARTPROXYPOLLERS=1 ZBX_PROXYCONFIGFREQUENCY=3600 ZBX_PROXYDATAFREQUENCY=1 ZBX_TLSCAFILE= ZBX_TLSCRLFILE= ZBX_TLSCERTFILE= ZBX_TLSKEYFILE=
Default values of these variables are specified after equal sign.
The allowed variables are identical of parameters in official
zabbix_server.conf. For example,
Please use official documentation for
zabbix_server.conf to get more information about the variables.
Allowed volumes for the Zabbix server container
The volume is used for custom alert scripts. It is
AlertScriptsPath parameter in
The volume is used by External checks (type of items). It is
ExternalScripts parameter in
The volume allows load additional modules and extend Zabbix server using
The volume is used to store TLS related files. These file names are specified using
The volume is used as location of public and private keys for SSH checks and actions. It is
SSHKeyLocation parameter in
The volume is used as location of of SSL client certificate files for client authentication. It is
SSLCertLocation parameter in
The volume is used as location of SSL private key files for client authentication. It is
SSLKeyLocation parameter in
The volume is used as location of certificate authority (CA) files for SSL server certificate verification. It is
SSLCALocation parameter in
The volume is used as location of
snmptraps.log file. It could be shared by
zabbix-snmptraps container and inherited using
volumes_from Docker option while creating new instance of Zabbix server.
SNMP traps processing feature could be enabled using shared volume and switched
ZBX_ENABLE_SNMP_TRAPS environment variable to
The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed to
The image variants
zabbix-server-pgsql images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
This image is based on the popular Alpine Linux project, available in the
alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as
bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the
alpine image description for examples of how to install packages if you are unfamiliar).
Supported Docker versions
This image is officially supported on Docker version 1.12.0.
Support for older versions (down to 1.6) is provided on a best-effort basis.
Please see the Docker installation documentation for details on how to upgrade your Docker daemon.
Documentation for this image is stored in the
server-pgsql/ directory of the
zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's
README.md file before attempting a pull request.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
Zabbix server does not support Jabber notifications on Alpine Linux because of
iksemel package is in testing repository and not available in stable repository.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
Why you don't add curl in the container?
Incorrect command: Container shell access and viewing Zabbix server logs
$ docker exec -ti some-zabbix-server-pgsql /bin/bash/
rpc error: code = 2 desc = oci runtime error: exec failed: exec: "/bin/bash/": stat /bin/bash/: not a directory
$ docker exec -ti some-zabbix-server-pgsql /bin/bash