README_v5.4.md

Zabbix Server 5.4

• Zabbix Server 5.4
  • Docker Compose Setup
    • Changes
  • UPDATE :: Zabbix Agent v2
  • What is Zabbix?
    • Zabbix Dockerfiles
      • Base Docker Image
      • Usage
    • Issues and Wiki
    • Contributing

Docker Compose Setup

This is a fork of the official Zabbix Server Repo with a few changes for a production setup:

Changes

1. Removed everything I don't need - this file only sets up the Zabbix Server with a Postgres backend, the Zabbix Server Dashboard frontend using NGINX and an Zabbix Agent 1 to monitor the server itself.
2. Added container names, container restart policies and fixed IP addresses (The Zabbix Agent Container IP is set to 172.16.239.106 - MAKE SURE to change the agent address from default 127.0.0.1 to 172.16.239.106 inside the Server Dashboard! see below).
3. Added an additional external network ingress_gateway that will be used by the system ingress to direct traffic to Zabbix. The web frontend container opens both port 8080 and 8443 to debug the initial setup (SSL will be handled by the Ingress and is not configured on port 8443). The ports can be commented out later. Make sure to either remove the ingress_gateway from the configuration file or add it manually docker network create ingress_gateway before starting the containers.

UPDATE :: Zabbix Agent v2

Using Zabbix Agent v2 (non-dockerized) for your Zabbix server:

1. Comment out zabbix-agent in the docker-compose file.
2. Install Agent 2:

wget https://repo.zabbix.com/zabbix/5.4/debian/pool/main/z/zabbix-release/zabbix-release_5.4-1%2Bdebian11_all.deb
dpkg -i zabbix-release_5.4-1+debian11_all.deb
apt update && apt install zabbix-agent2

3. Configure Agent v2 - see potential issue:

/etc/zabbix/zabbix_agent2.conf

# This is a configuration file for Zabbix agent 2 (Unix)
PidFile=/var/run/zabbix/zabbix_agent2.pid
LogFile=/var/log/zabbix/zabbix_agent2.log
LogFileSize=100
DebugLevel=3
Server=172.16.238.101
ListenPort=10050
Hostname=zabbix_server
Include=/etc/zabbix/zabbix_agent2.d/*.conf
ControlSocket=/tmp/agent.sock
TLSConnect=psk
TLSAccept=psk
TLSPSKIdentity=zabbix_server
TLSPSKFile=/opt/zabbix/agent_tls.psk
Plugins.Docker.Endpoint=unix:///var/run/docker.sock

Point your agent on your host system towards to docker container running the Zabbix server (see Docker-Compose file for IP, default = 172.16.238.101). And generate the pre shared key in /opt/zabbix/agent_tls.psk:

openssl rand -hex 32 > /opt/zabbix/agent_tls.psk

The server now has to be pointed to the Zabbix Server WAN IP:

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

• alpine
• centos till Zabbix 5.0
• oracle linux from Zabbix 5.0
• ubuntu

Important information: All Zabbix images based on CentOS 8 image can not be updated anymore because CentOS 8 base image is outdated (base image is not updated for half year). Because of that all images based on CentOS 8 replaced with Oracle Linux 8 as base 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-web-service - Zabbix web service 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.