-
New Feature Request
-
Resolution: Fixed
-
Trivial
-
None
Disabling the housekeeper becomes a recommendation when it can't keep up with the size of the history tables. In such cases external housekeeping needs to be performed (like deleting table partitions). In many situations I'd like to keep most of the housekeeper functionality for tables that don't cause any problems (such as trends or alerts) while using an external cleanup for the problematic tables (history_uint) for example.
I suggest adding fine grained control over which tasks are performed by the housekeeper. Something like:
DisableHousekeeping=history_uint,history
instead of simply
DisableHousekeeping=1
- causes
-
ZBX-14312 Proxy->Agent communication drops intermittently
- Closed
- is duplicated by
-
ZBXNEXT-1539 Housekeeper does not delete deleted items/hosts which should be cleaned up and other cleanup that should be done
- Open
-
ZBXNEXT-699 Support for global history (and potentially trends) maximum
- Closed
-
ZBXNEXT-953 Zabbix write into housekeeper table with disabled housekeeper option
- Closed
-
ZBXNEXT-30 simplify housekeeper configuration
- Closed
-
ZBXNEXT-1039 Hide keep history and keep trends from items for databases with partitioning
- Closed