mirror of
https://github.com/zabbix/zabbix-docker.git
synced 2025-01-10 15:48:38 +01:00
41 lines
1.6 KiB
Plaintext
41 lines
1.6 KiB
Plaintext
### Option: HousekeepingFrequency
|
|
# How often Zabbix will perform housekeeping procedure (in hours).
|
|
# Housekeeping is removing outdated information from the database.
|
|
# To prevent Housekeeper from being overloaded, no more than 4 times HousekeepingFrequency
|
|
# hours of outdated information are deleted in one housekeeping cycle, for each item.
|
|
# To lower load on server startup housekeeping is postponed for 30 minutes after server start.
|
|
# With HousekeepingFrequency=0 the housekeeper can be only executed using the runtime control option.
|
|
# In this case the period of outdated information deleted in one housekeeping cycle is 4 times the
|
|
# period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.
|
|
#
|
|
# Mandatory: no
|
|
# Range: 0-24
|
|
# Default:
|
|
# HousekeepingFrequency=1
|
|
|
|
HousekeepingFrequency=${ZBX_HOUSEKEEPINGFREQUENCY}
|
|
|
|
### Option: MaxHousekeeperDelete
|
|
# The table "housekeeper" contains "tasks" for housekeeping procedure in the format:
|
|
# [housekeeperid], [tablename], [field], [value].
|
|
# No more than 'MaxHousekeeperDelete' rows (corresponding to [tablename], [field], [value])
|
|
# will be deleted per one task in one housekeeping cycle.
|
|
# If set to 0 then no limit is used at all. In this case you must know what you are doing!
|
|
#
|
|
# Mandatory: no
|
|
# Range: 0-1000000
|
|
# Default:
|
|
# MaxHousekeeperDelete=5000
|
|
|
|
MaxHousekeeperDelete=${ZBX_MAXHOUSEKEEPERDELETE}
|
|
|
|
### Option: ProblemHousekeepingFrequency
|
|
# How often Zabbix will delete problems for deleted triggers (in seconds).
|
|
#
|
|
# Mandatory: no
|
|
# Range: 1-3600
|
|
# Default:
|
|
# ProblemHousekeepingFrequency=60
|
|
|
|
ProblemHousekeepingFrequency=${ZBX_PROBLEMHOUSEKEEPINGFREQUENCY}
|