Host with two uptime check items

[cesarsj]

The TI departmental servers we monitor on Zabbix are Windows, so we use the Windows Template on it. However, six servers restart every day at midnight.

I'd like to create another uptime check item, with flexible range: 1-7: 00: 15-24: 00, so that the {HOST.NAME} has just been restarted trigger only fires within that range. That is, skipping the time when rebooting is not a problem, but routine.

But as I try to add a new uptime check item, it appears that I can't add another with a key that already exists.
What can I do then? I can't delete the existing item because of the template, other servers and history we need to keep. Would I like to parameterize the trigger to be fired only at a certain time?

[sancho]

Hi cesarsj
Sorry but I don't understand, why don't you configure the interval in the template item on each server?

[cesarsj]

Hi cesarsj
Sorry but I don't understand, why don't you configure the interval in the template item on each server?

Hi, sancho
Because for the other Windows servers, which have no reboot routine, I want to continue the default template range.

[AvaTTaR]

You can disconnect this host from template, and edit it, or logically for zabbix - create a maintenance time-range for this host..

[sancho]

cesarsj
This item, even if it is dependent on a template, you can configure the interval that interests you on each of the 6 servers.
You don't have to modify it in the template, only in the host's own item.
The changes you make to the host item only affect that host, even if the item is from a template.

But surely even if you did the alert would be activated again when you received the first value after the interval.

The best thing is what AvaTTaR indicates, it creates a daily maintenance for the hours you indicate and puts in that maintenance the 6 servers.

I'm sorry for my google english.

[cesarsj]

sancho
Really I was wrong, I thought that changing the range on the host would also change in the template, and this does not happen. The solution with that would be quite easy.

But now I come across another question. Our Zabbix is a migration from version 1.8.11 to version 4.0.5. And in the old version, the trigger {HOST.NAME} has just been restarted had in its expression 'last (0)} <600. We inherited it. And in version 4.0 the expression has change (0)} <0.

I wish I would adjust to the new default, but if I change it, the solution would no longer work.

AvaTTaR
The daily maintenance solution wouldn't work either, I believe.

But why would 'change (0)} <0' be better than 'last (0)} <600'? Do I leave the trigger with the expression of version 1.8.11?

'If I change to 'change (0)} <0' in the templates, I think for only these hosts I'll leave last (0)} <600'