-
Problem report
-
Resolution: Won't fix
-
Major
-
None
-
4.0.11
-
None
-
apache2 2.4.25-3+deb9u7 amd64
apache2-bin 2.4.25-3+deb9u7 amd64
apache2-data 2.4.25-3+deb9u7 all
apache2-utils 2.4.25-3+deb9u7 amd64
default-mysql-client 1.0.2 all
libapache2-mod-php 1:7.0+49 all
libapache2-mod-php7.0 7.0.33-0+deb9u3 amd64
libdbd-mysql-perl 4.041-2 amd64
mysql-client 5.5.9999+default amd64
mysql-common 5.8+1.0.2 all
php-mysql 1:7.0+49 all
php7.0-mysql 7.0.33-0+deb9u3 amd64
zabbix-agent 1:4.0.11-1+stretch amd64
zabbix-frontend-php 1:4.0.11-1+stretch all
zabbix-release 1:4.0-3+stretch all
zabbix-server-mysql 1:4.0.11-1+stretch amd64apache2 2.4.25-3+deb9u7 amd64 apache2-bin 2.4.25-3+deb9u7 amd64 apache2-data 2.4.25-3+deb9u7 all apache2-utils 2.4.25-3+deb9u7 amd64 default-mysql-client 1.0.2 all libapache2-mod-php 1:7.0+49 all libapache2-mod-php7.0 7.0.33-0+deb9u3 amd64 libdbd-mysql-perl 4.041-2 amd64 mysql-client 5.5.9999+default amd64 mysql-common 5.8+1.0.2 all php-mysql 1:7.0+49 all php7.0-mysql 7.0.33-0+deb9u3 amd64 zabbix-agent 1:4.0.11-1+stretch amd64 zabbix-frontend-php 1:4.0.11-1+stretch all zabbix-release 1:4.0-3+stretch all zabbix-server-mysql 1:4.0.11-1+stretch amd64
Steps to reproduce:
- Install a clean Debian 9 OS. Mine will be 9.8.0 amd64.
- Follow the installation steps. By the time of writing this report, zabbix-release_4.0-3+stretch_all.deb repository package was already released, whereas documentation lists instructions for version 4.0-2. I have made the upgrade during installation, in case it matters.
- Once Zabbix Server, Zabbix Agent and Zabbix Web Interface components have been installed, navigate to web interface and create:
1 host group for your tests. This can be skipped; is done only for filtering convenience.
1 template containing a single item check with update interval 1 hour. This item has icmpping[google.com] key.
5 hosts as members of the test host group and with the test template attached to them.
You can find template and hosts export in attachments for testing convenience. - Wait a couple hours.
Result:
Here are results I have had produced:
| HOST 1 | HOST 2 | HOST 3 | HOST 4 | HOST 5 | |
|---|---|---|---|---|---|
| Time of check 1 | 2019-08-14 08:00:02 | 2019-08-14 08:00:03 | 2019-08-14 08:00:04 | 2019-08-14 08:00:05 | 2019-08-14 08:00:06 |
| Time of check 2 | 2019-08-14 09:00:02 | 2019-08-14 09:00:03 | 2019-08-14 09:00:04 | 2019-08-14 09:00:05 | 2019-08-14 09:00:06 |
| Time of check 3 | 2019-08-14 10:00:02 | 2019-08-14 10:00:03 | 2019-08-14 10:00:04 | 2019-08-14 10:00:05 | 2019-08-14 10:00:06 |
You can also find poller load graph for this period in attachments.
Expected:
I remember during Zabbix trainings for version 3.0 we were told Zabbix Server automatically analyzes the amount of hosts, items and their update intervals to automatically allocate checks in time (this would only work in case custom intervals are not used, of course). This ensured Zabbix Server does not perform checks in batches, providing best performance. I have not read all the upgrade notes of all versions between 3.0 and 4.0, but I do believe this is an essential Zabbix feature not worth removing.
With this being said, I expected the checks to happen evenly thoughout the time: approximately one check per 12 minutes. Not 5 checks per 5 seconds in 1 hour interval as it happens now - there is no scheduling in that.
I have observed this for quite some time on our pre-production environment, where checks are performed once per 12 hours. You can find a screenshot of poller load in attachments. It shows poller load before we detected and issue and after we disabled the most resource-consuming one. That environment has exactly same symptoms of check intervals being completely off.
Let me know if you would require additional information.
