-
Incident report
-
Resolution: Duplicate
-
Major
-
None
-
2.2.9
Time based triggers produced false-positive alerts at the same time for a couple of days.
These are obviously caused by busy history syncer processes.
While everything seams to be fine on Zabbix server side (resources, database, nvps, ...) there were thousands of suspicious VMware related log messages that matched exactly in time:
--- SNIP zabbix_server.log --- 895:20150430:020102.946 item "50196356-038e-d219-ca5b-52460e478ba1:vmware.vm.memory.size.compressed[{$URL},{HOST.HOST}]" became not supported: Couldn't connect to server 895:20150430:020102.946 item "502d13c2-bffe-b0e7-c4a2-2232b8f5d214:vmware.vm.memory.size.compressed[{$URL},{HOST.HOST}]" became not supported: Couldn't connect to server 895:20150430:020102.946 item "502df28b-5daf-e7a4-cb42-f874507238f4:vmware.vm.memory.size[{$URL},{HOST.HOST}]" became not supported: Couldn't connect to server 895:20150430:020102.946 item "5019e168-2dc5-223d-a82c-c857b98698c3:vmware.vm.memory.size.compressed[{$URL},{HOST.HOST}]" became not supported: Couldn't connect to server 895:20150430:020102.946 item "5019e5ed-810f-dfa8-9577-9127c99439b3:vmware.vm.uptime[{$URL},{HOST.HOST}]" became not supported: Couldn't connect to server 895:20150430:020102.946 item "502d8262-815b-8ff3-c7c5-7ef0e61bbdb9:vmware.vm.memory.size.compressed[{$URL},{HOST.HOST}]" became not supported: Couldn't connect to server --- SNAP zabbix_server.log ---
After creating a maintenance period with no data collection (1h at 02:00am and 04:00am) for all VMware hosts, the Zabbix server was not suffering from busy history syncer processes anymore.
Environment
- 1 vCenter
- 20 Hypervisors
- >350 Virtual Machines
- VMware monitoring done by Zabbix proxy
- duplicates
-
ZBXNEXT-3051 Count of actions has a significant impact on event processing
-
- Closed
-