-
New Feature Request
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
Issue:
When log monitoring creates only problem events and no recovery, the number of unresolved problems can grow very large (e.g. 5M+).
Impact:
- Causes heavy CPU and I/O load on the DB and Zabbix server
- Slows down problem-related GUI pages and widgets
Suggestion:
Show a warning in System Information if too many unresolved problems exist (for example, over 1M).
Also suggest users to review their log monitoring settings or clean up old problems.
We should recommend keeping the problem table clean and advise users to tune their log settings if necessary.
Add Info:
From ZBXNEXT-10208. It’s a duplicate, but it’s a real case that occurred due to large problem tables. I’ll move the details here.
When a large number of problems remain unresolved for a long time, it can cause heavy DB load and slow queries
- In dashboards and problem views
- During trigger housekeeper cleanup (see ZBX-26887)
Requested improvement:
Notify administrators when unresolved problems accumulate
- UI warning
- log messages, or internal monitoring item.
Benefits:
Helps detect abnormal increase of problems early
Prevents performance issues in large environments
- is duplicated by
-
ZBXNEXT-10208 Provide notifications when many unresolved problems remain
-
- Closed
-
- related to
-
ZBX-26887 Trigger housekeeper causes heavy DB load when many triggers are deleted
-
- Confirmed
-