[ZBX-21387] Zabbix server queue has increased significantly. Created: 2022 Jul 26  Updated: 2022 Jul 27  Resolved: 2022 Jul 27

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 6.0.6
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Vadim Assignee: Zabbix Support Team
Resolution: Commercial support required Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS Linux 8
Postgresql 13 + timescaledb extension 2.3.0
Zabbix server 6.0.6

Attachments: PNG File first.png     PNG File second.png    

 Description   

Steps to reproduce:

  1. update zabbix server from 5.4 to 6.0.6 version
  2. Check Zabbix server queue graphs before and after update

Result:
Zabbix queue graph shows significant growth
Expected:
no changes in zabbisx queue

On attached screenshots we can see situation before update (first) and after update (second) for "Zabbix queue" item with key "zabbix[queue]". 
No configuration change was performed
No errors in logs for zabbix server on database
Overall situation is the same exept for zabbix version changed. 

Has something changed in the way how zabbix queu ceck is performed?
How does that parameter affects zabbix performance? 
Should we do somthing about that queue, or momentum zabbix queue (<5 sec ) is OK? 

 Comments   
Comment by Dmitrijs Lamberts [ 2022 Jul 27 ]

Please be advised that this section of the tracker is for bug reports only. The case you have submitted can not be qualified as one, so please reach out to [email protected] for commercial support (https://zabbix.com/support) or consultancy services. Alternatively, you can also use our IRC channel or community forum (https://www.zabbix.com/forum) for assistance. With that said, we are closing this ticket. Thank you for understanding.

Generated at Mon Apr 21 08:15:55 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.