Understanding template triggers

[Mounty]

Hello, I'm using Zabbix 6.0 on OmniOS (OpenSolaris/Illumos derivative) and am struggling to understand the supplied templates.
I can understand why you might want to know that a server has been restarted but what I don't understand is that the template does not allow for manual closure. In fact, I don't see how to get rid of this entry from the problems page. Surely you would just wish to be advised that the server has been restarted, and then remove the message? Also, it doesn't make sense anyway, since I've not actually got the Zabbix agent working on the machine called Cortex (I'm asking elsewhere for help on that), so how can there be any other problems on that machine? Is it possible that there are some stray datapoints for the item, and if so, how can I delete them?
Here's more detail about the problem:

[cyber]

You can always edit the template and add that tickmark there for "allow manual close"
But that trigger is based on "change" function .. "change(/Template OS Solaris/system.uptime)<0". It should return to normal after next check, when you receive again increased value for uptime.
How exactly it can be calculated from nonexisting data, is beyond me right now and I don't have time to experiment.

[cyber]

You can always edit the template and add that tickmark there for "allow manual close"
But that trigger is based on "change" function .. "change(/Template OS Solaris/system.uptime)<0". It should return to normal after next check, when you receive again increased value for uptime.
How exactly it can be calculated from nonexisting data, is beyond me right now and I don't have time to experiment.

[Mounty]

OK, so once I get the Zabbix agent working again on that server, the warning should disappear. Thanks.