There are multiple approaches to running Zabbix in docker. Install the Zabbix 6. This will add the necessary Zabbix 6. Start Zabbix components and observe the log file. You should see that the database schema upgrade is in progress. Once it has finished, all of the internal Zabbix processes should be started without any issues:. In addition, we are also required to update our Zabbix proxies. The procedure is very similar to what we did in our previous steps:.
For Zabbix proxies using SQLite3 backend databases, automatic database schema upgrade is not supported. We will simply have to remove the old SQLite3 database file — it will then be automatically recreated once we start the Zabbix proxy.
After the upgrade to Zabbix 6. Zabbix 6. These tables now contain primary keys. The upgrade or these history tables is not done automatically since it can cause additional downtime. Depending on the size of the database, executing the required changes can be extremely slow since every record in the history tables needs to be altered. You should learn to work with Docker and to create custom images.
When creating environments using Docker, you should be careful. The Docker environment has some internal networks, which can be in conflict with the physical network. So, it is necessary to change the default networks — Docker network overlay and Docker bridge. Docker Swarm is already used to monitor extremely large environments with over 90, and over 50 proxies. I think it is possible, though scaling Zabbix with Kubernetes is more complex than with Docker Swarm.
Contents I. Zabbix project requirements II. The Zabbix environment needed to meet the following requirements: to monitor more than 3, NVPS; to be fault-tolerant; to be resilient; to scale the environment horizontally. Initially, the instance was divided into various components. Accessing the frontend. HAProxy configuration file haproxy. Swarm consists of one or more nodes.
The cluster can be of two types: Managers that are responsible for managing the cluster and can perform workloads.
Workers that are responsible for performing the services or the loads. Reverse Proxy can be executed using nginx and traefik. Compose file and Deploy The Compose file —. Reverse Proxy Here is the example of configuring Reverse Proxy using traefik. Finally, we define the command to be executed after the container is started. For this Zabbix, Server traefik is not enabled.
In this case, we can use environment 5. Here, we can define, for instance, database address, database username, number of pollers we will start, the path for external and alert scripts, and other options.
In this example, we use two volumes — for external scripts and for alert scripts that must be stored in the NFS Server. Here, 5 replicas mean that we can start 5 Zabbix frontends. This can be used for more extensive environments, which also means that we have 5 containers and 5 connections. If we use a different name, access to the frontend will not be available. The load balancer server port defines to which port the container is listening and where the official Zabbix frontend image is stored.
Up to now, deployment has been done manually. You needed to connect to one of the services with the Docker Swarm Manager function, enter the NFS directory, and deploy the service:. Typically, Docker official images from Zabbix are used. However, for the Zabbix Server and Zabbix Proxy is not enough. In production environments, additional patches are needed — scripts, ODBC drivers to monitor the database. You should learn to work with Docker and to create custom images.
When creating environments using Docker, you should be careful. The Docker environment has some internal networks, which can be in conflict with the physical network. So, it is necessary to change the default networks — Docker network overlay and Docker bridge. Docker Swarm is already used to monitor extremely large environments with over 90, and over 50 proxies.
I think it is possible, though scaling Zabbix with Kubernetes is more complex than with Docker Swarm. First to know is that we are using three separate containers. Create a new directory within the shared Docker directory which is created when installing Docker. I called it Zabbix:. Create a volume within this container and point it to the newly create directory:. As far as I can see, we just need to start up the container for one time, afterwards we can ignore the container.
The number of tags per event tags depends on configuration. The table contains formulas that can be used to calculate the disk space required for Zabbix system:. Database size will grow then it will stop growing at some point, which depends on housekeeper settings.
It is very important to have precise system time on the server with Zabbix running. It's strongly recommended to maintain synchronized system time on all systems Zabbix components are running on.
Supported 5. Sidebar Zabbix documentation. Zabbix Manual. Zabbix processes. Best practices for secure Zabbix setup. Building Zabbix agent 2 on Windows. Building Zabbix agent on macOS. Building Zabbix agent on Windows. Upgrade from packages. Upgrade from sources.
Zabbix appliance. Additional JavaScript objects. Windows-specific item keys. Zabbix agent 2. VMware monitoring item keys. Aggregate calculations. Standardized templates for network devices. HTTP template operation. IPMI template operation.
JMX template operation. ODBC template operation. Zabbix agent 2 template operation. Zabbix agent template operation. Webhook script examples. Service monitoring. Web monitoring. Virtual machine monitoring.
0コメント