[ZBX-137] Database statistics Created: 2007 Nov 04  Updated: 2017 May 30  Resolved: 2009 Jun 30

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 1.4.2
Fix Version/s: None

Type: Incident report Priority: Minor
Reporter: Lukas Macura Assignee: Alexei Vladishev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Zabbix server should take care of time it spent to save data into DB. It happens sometimes that mysql is slow because many items in histrory/trends. Zabbix should take care of this and be able to do some alerting based on this. It is really hard for user to find why monitoring does not work or why only part of datas are in history. It would be enaught to make housekeeper some intelligent work to check if queue was run in all or not. It could solve problem even with many unreachable hosts. Maybe to create some trigger using zabbix[queue] internal parameter and to put it with some triggers to basic zabbix templates?

In fact, there should be kind of errors (like this, database connection problems or server is not runing) which should have absolutely precedence in zabbix and should be visible just after login (maybe some popup window) ?



 Comments   
Comment by Lukas Macura [ 2009 Feb 10 ]

There is "zabbix performance" in main screen. It shows how many items per seconds need zabbix to work good. I think we can close it for now.

Comment by Alexei Vladishev [ 2009 Jun 30 ]

I am closing it on request.

Generated at Thu Apr 25 01:47:20 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.