Hello,
Im deploying a zabbix server in our facility and Im having some problems.
-In the initial stage, there was few servers and we defined them as host, without using templates. Some time later, the number of monitored hosts grew constantly so we need to switch to templates.
Is there a way to achieve this without losing the history of every host? If I link a template that contains the same item zabbix complains about duplicate key
-I dont understand what is a maintenance period and how relates with rest of zabbix concepts.
do the triggers are fired during a maintenance period?
in a maintenance with data collection, this time how is represented in a availability period? is computed as KO or unknown ?
Thanks !
PS: using zabbix v2.0.2
Im deploying a zabbix server in our facility and Im having some problems.
-In the initial stage, there was few servers and we defined them as host, without using templates. Some time later, the number of monitored hosts grew constantly so we need to switch to templates.
Is there a way to achieve this without losing the history of every host? If I link a template that contains the same item zabbix complains about duplicate key
-I dont understand what is a maintenance period and how relates with rest of zabbix concepts.
do the triggers are fired during a maintenance period?
in a maintenance with data collection, this time how is represented in a availability period? is computed as KO or unknown ?
Thanks !
PS: using zabbix v2.0.2