Zabbix Documentation 3.0

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:appendix:config:zabbix_server

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:appendix:config:zabbix_server [2020/02/13 12:50]
martins-v adding warning on MaxHousekeeperDelete
manual:appendix:config:zabbix_server [2020/02/13 12:51] (current)
martins-v adding more warning on MaxHousekeeperDelete
Line 41: Line 41:
 | LogType| no | | file |Log output type:\\ //file// - write log to file specified by LogFile parameter,​\\ //system// - write log to syslog,\\ //console// - write log to standard output.\\ This parameter is supported since Zabbix 3.0.0. | | LogType| no | | file |Log output type:\\ //file// - write log to file specified by LogFile parameter,​\\ //system// - write log to syslog,\\ //console// - write log to standard output.\\ This parameter is supported since Zabbix 3.0.0. |
 | LogSlowQueries| no | 0-3600000 |0 |How long a database query may take before being logged (in milliseconds).\\ 0 - don't log slow queries.\\ This option becomes enabled starting with DebugLevel=3.\\ This parameter is supported since Zabbix 1.8.2. ​ | | LogSlowQueries| no | 0-3600000 |0 |How long a database query may take before being logged (in milliseconds).\\ 0 - don't log slow queries.\\ This option becomes enabled starting with DebugLevel=3.\\ This parameter is supported since Zabbix 1.8.2. ​ |
-| MaxHousekeeperDelete| no | 0-1000000 |5000 |No more than '​MaxHousekeeperDelete'​ rows (corresponding to [tablename],​ [field], [value]) will be deleted per one task in one housekeeping cycle.\\ SQLite3 does not use this parameter, deletes all corresponding rows without a limit.\\ If set to 0 then no limit is used at all. In this case you must know what you are doing!\\ This parameter is supported since Zabbix 1.8.2 and applies only to deleting history and trends of already deleted items. ​ |+| MaxHousekeeperDelete| no | 0-1000000 |5000 |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, so as not to [[zabbix_server#​footnotes|overload the database!]] **<​sup>​[[zabbix_server#​footnotes|1]]</​sup>​**\\ This parameter is supported since Zabbix 1.8.2 and applies only to deleting history and trends of already deleted items. ​ |
 | PidFile| no | |/​tmp/​zabbix_server.pid |Name of PID file. | | PidFile| no | |/​tmp/​zabbix_server.pid |Name of PID file. |
 | ProxyConfigFrequency| no | 1-604800 | 3600 | How often Zabbix server sends configuration data to a Zabbix proxy in seconds. Used only for proxies in a passive mode.\\ This parameter is supported since Zabbix 1.8.3. | | ProxyConfigFrequency| no | 1-604800 | 3600 | How often Zabbix server sends configuration data to a Zabbix proxy in seconds. Used only for proxies in a passive mode.\\ This parameter is supported since Zabbix 1.8.3. |