Official Zabbix Dockerfiles
Go to file
2019-06-26 18:18:14 +03:00
agent Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
java-gateway Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
proxy-mysql Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
proxy-sqlite3 Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
server-mysql Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
server-pgsql Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
snmptraps Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
web-apache-mysql Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
web-apache-pgsql Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
web-nginx-mysql Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
web-nginx-pgsql Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
zabbix-appliance Zabbix v4.0.10 release 2019-06-26 18:18:14 +03:00
.env_agent Added SourceIP and ListenIP params 2017-05-11 03:37:37 -07:00
.env_db_mysql Added compose files for 2.0 2016-08-11 14:16:42 -07:00
.env_db_mysql_proxy Added compose files for 2.0 2016-08-11 14:16:42 -07:00
.env_db_pgsql Fixed PostgreSQL custom schema usage 2019-04-11 19:41:44 +03:00
.env_java Added compose files for 2.0 2016-08-11 14:16:42 -07:00
.env_prx Updated docker compose variables 2018-02-20 06:50:59 -08:00
.env_prx_mysql Added compose files for 2.0 2016-08-11 14:16:42 -07:00
.env_prx_sqlite3 Added compose files for 2.0 2016-08-11 14:16:42 -07:00
.env_srv Added HistoryStorageDateIndex for Zabbix server 2018-10-04 13:42:30 +03:00
.env_web Added ZBX_SESSION_NAME for Zabbix frontend 2019-01-14 00:55:56 +02:00
.gitignore Fixed issue with init (PID 1) 2019-04-09 22:43:56 +03:00
build.sh Fixed SVN -> GIT 2019-06-12 18:00:18 +03:00
docker-compose_v3_alpine_mysql_latest.yaml Prepare for MySQL 8.0 2019-04-10 02:09:09 +03:00
docker-compose_v3_alpine_mysql_local.yaml Prepare for MySQL 8.0 2019-04-10 02:09:09 +03:00
docker-compose_v3_alpine_pgsql_latest.yaml Merge branch 'master' into 4.0 2019-04-19 00:00:06 +03:00
docker-compose_v3_alpine_pgsql_local.yaml Merge branch 'master' into 4.0 2019-04-19 00:00:06 +03:00
docker-compose_v3_centos_mysql_latest.yaml Prepare for MySQL 8.0 2019-04-10 02:09:09 +03:00
docker-compose_v3_centos_mysql_local.yaml Prepare for MySQL 8.0 2019-04-10 02:09:09 +03:00
docker-compose_v3_centos_pgsql_latest.yaml Merge branch 'master' into 4.0 2019-04-19 00:00:06 +03:00
docker-compose_v3_centos_pgsql_local.yaml Merge branch 'master' into 4.0 2019-04-19 00:00:06 +03:00
docker-compose_v3_ubuntu_mysql_latest.yaml Prepare for MySQL 8.0 2019-04-10 02:09:09 +03:00
docker-compose_v3_ubuntu_mysql_local.yaml Prepare for MySQL 8.0 2019-04-10 02:09:09 +03:00
docker-compose_v3_ubuntu_pgsql_latest.yaml Merge branch 'master' into 4.0 2019-04-19 00:00:06 +03:00
docker-compose_v3_ubuntu_pgsql_local.yaml Merge branch 'master' into 4.0 2019-04-19 00:00:06 +03:00
kubernetes.yaml Fixed kubernetes reciept 2019-04-01 16:12:07 +03:00
LICENSE Initial commit 2016-08-03 10:36:02 +03:00
README.md Updated README information 2019-01-12 23:07:44 +02:00

logo

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.

For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

Zabbix Dockerfiles

This repository contains Dockerfile of Zabbix for Docker's automated build published to the public Docker Hub Registry.

Base Docker Image

Usage

Please follow usage instructions of each Zabbix component image:

Issues

If you have any problems with or questions about this image, please contact us through a GitHub issue.

Contributing

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.