Zabbix Documentation 2.2

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

User Tools

Site Tools


manual:web_interface:frontend_sections:administration:general

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
manual:web_interface:frontend_sections:administration:general [2017/12/12 10:30]
natalja.cernohajeva
manual:web_interface:frontend_sections:administration:general [2019/07/11 08:25] (current)
martins-v the first attempt to reactivate the unsupported item may occur earlier than the value configured here
Line 144: Line 144:
  
 ^Parameter^Description^ ^Parameter^Description^
-|//Refresh unsupported items (in sec)// ​ |Some items may become unsupported due to errors in user parameters or because of an item not being supported by agent. Zabbix can be configured to periodically make unsupported items active.\\ Zabbix will activate unsupported item every N seconds set here. If set to 0, the automatic activation will be disabled.\\ The configured value also applies to how often Zabbix proxies reactivate unsupported items. ​ |+|//Refresh unsupported items (in sec)// ​ |Some items may become unsupported due to errors in user parameters or because of an item not being supported by agent. Zabbix can be configured to periodically make unsupported items active.\\ Zabbix will activate unsupported item every N seconds set here. If set to 0, the automatic activation will be disabled.\\ Note that the first attempt to reactivate the unsupported item may occur earlier than the value configured here.\\ The configured value also applies to how often Zabbix proxies reactivate unsupported items. ​ |
 |//Group for discovered hosts// ​ |Hosts discovered by [[manual:​discovery:​network_discovery|network discovery]] and [[manual:​discovery:​auto_registration|agent auto-registration]] will be automatically placed in the host group, selected here.  | |//Group for discovered hosts// ​ |Hosts discovered by [[manual:​discovery:​network_discovery|network discovery]] and [[manual:​discovery:​auto_registration|agent auto-registration]] will be automatically placed in the host group, selected here.  |
 |//User group for database down message// ​ |User group for sending alarm message or '​None'​.\\ Availability of Zabbix server depends on availability of backend database. It cannot work without a database. Database watchdog, a special Zabbix server process, will alarm selected users in case of disaster. If the database is down, the watchdog will send notifications to the user group set here, using all configured user media entries. Zabbix server will not stop; it will wait until the database is back again to continue processing. The watchdog tries to establish a new connection to the database every 60 seconds. If the database is still down the watchdog repeats sending alerts, but not more often than every 15 minutes. ​  \\ //Note//: Until Zabbix version 1.8.2 database watchdog was supported for MySQL only. Since 1.8.2, it is supported for all databases. ​ | |//User group for database down message// ​ |User group for sending alarm message or '​None'​.\\ Availability of Zabbix server depends on availability of backend database. It cannot work without a database. Database watchdog, a special Zabbix server process, will alarm selected users in case of disaster. If the database is down, the watchdog will send notifications to the user group set here, using all configured user media entries. Zabbix server will not stop; it will wait until the database is back again to continue processing. The watchdog tries to establish a new connection to the database every 60 seconds. If the database is still down the watchdog repeats sending alerts, but not more often than every 15 minutes. ​  \\ //Note//: Until Zabbix version 1.8.2 database watchdog was supported for MySQL only. Since 1.8.2, it is supported for all databases. ​ |
 |//Log unmatched SNMP traps// ​ |Log [[manual:​config:​items:​itemtypes:​snmptrap|SNMP trap]] if no corresponding SNMP interfaces have been found. ​ | |//Log unmatched SNMP traps// ​ |Log [[manual:​config:​items:​itemtypes:​snmptrap|SNMP trap]] if no corresponding SNMP interfaces have been found. ​ |