| .github | ||
| agent | ||
| agent2 | ||
| java-gateway | ||
| proxy-mysql | ||
| proxy-sqlite3 | ||
| server-mysql | ||
| server-pgsql | ||
| snmptraps | ||
| web-apache-mysql | ||
| web-apache-pgsql | ||
| web-nginx-mysql | ||
| web-nginx-pgsql | ||
| web-service | ||
| zabbix-appliance/rhel | ||
| .env_agent | ||
| .env_db_mysql | ||
| .env_db_mysql_proxy | ||
| .env_db_pgsql | ||
| .env_java | ||
| .env_prx | ||
| .env_prx_mysql | ||
| .env_prx_sqlite3 | ||
| .env_srv | ||
| .env_web | ||
| .env_web_service | ||
| .gitignore | ||
| .MYSQL_PASSWORD | ||
| .MYSQL_ROOT_PASSWORD | ||
| .MYSQL_USER | ||
| .POSTGRES_PASSWORD | ||
| .POSTGRES_USER | ||
| build.sh | ||
| docker-compose_v3_alpine_mysql_latest.yaml | ||
| docker-compose_v3_alpine_mysql_local.yaml | ||
| docker-compose_v3_alpine_pgsql_latest.yaml | ||
| docker-compose_v3_alpine_pgsql_local.yaml | ||
| docker-compose_v3_centos_mysql_latest.yaml | ||
| docker-compose_v3_centos_mysql_local.yaml | ||
| docker-compose_v3_centos_pgsql_latest.yaml | ||
| docker-compose_v3_centos_pgsql_local.yaml | ||
| docker-compose_v3_ubuntu_mysql_latest.yaml | ||
| docker-compose_v3_ubuntu_mysql_local.yaml | ||
| docker-compose_v3_ubuntu_pgsql_latest.yaml | ||
| docker-compose_v3_ubuntu_pgsql_local.yaml | ||
| generate-stackbrew-library.sh | ||
| kubernetes.yaml | ||
| LICENSE | ||
| README.md | ||
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
There is some documentation and examples in the official Zabbix Documentation!
Please also follow usage instructions of each Zabbix component image:
-
zabbix-appliance - Zabbix appliance with built-in MySQL server, Zabbix server, Zabbix Java Gateway and Zabbix frontend based on Nginx web-server
Important information: Zabbix Docker Appliance has been decommissioned (except Red Hat edition) and will not be available for 3.0.31, 4.0.19, 4.4.7, 5.0.0 and newer releases. Please use a separate Docker images for each component instead of the all-in-one solution.
-
zabbix-agent - Zabbix agent
-
zabbix-agent2 - Zabbix agent 2
-
zabbix-server-mysql - Zabbix server with MySQL database support
-
zabbix-server-pgsql - Zabbix server with PostgreSQL database support
-
zabbix-web-apache-mysql - Zabbix web interface on Apache2 web server with MySQL database support
-
zabbix-web-apache-pgsql - Zabbix web interface on Apache2 web server with PostgreSQL database support
-
zabbix-web-nginx-mysql - Zabbix web interface on Nginx web server with MySQL database support
-
zabbix-web-nginx-pgsql - Zabbix web interface on Nginx web server with PostgreSQL database support
-
zabbix-proxy-sqlite3 - Zabbix proxy with SQLite3 database support
-
zabbix-proxy-mysql - Zabbix proxy with MySQL database support
-
zabbix-java-gateway - Zabbix Java Gateway
-
zabbix-zabbix-web-service - Zabbix web servce for performing various tasks using headless web browser (for example, reporting)
-
zabbix-snmptraps - Additional container image for Zabbix server and Zabbix proxy to support SNMP traps
Issues and Wiki
Be sure to check the Wiki-page on common problems and questions. If you still have problems with or questions about the images, 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.