Ack Zabbix Agent is not available when server is shutdown intentionally

[cbass]

Zabbix Server: 5.05
Server OS: Ubuntu 20.04
DB: MySql 8.0.22

Hello, I have what I expect is a basic question but I was unable to find any previous topic's in the forum related to my question.

So we have a few Windows Servers that are in AWS and/or Azure cloud. These servers are sometimes shutdown for various reasons throughout the day. As an example, I shutdown a server that has the Zabbix Agent 2 installed. I get the problem notification on the dashboard "Zabbix agent is not available" and Ack the problem. I then get my notifications that it has been resolved but shortly after I get another notification that "Zabbix agent is not available".

So my question is, how would you/anyone recommend dealing with these sort of systems and notifications? I understand why the alert and notification continue after ack'ing it but is there a way to ack and tell it not to keep alerting?

Thank you in advance!

[cbass]

To follow up on my previous question, would it make sense to configure a time based trigger(s) and if so, how would you recommend going about this? So far, I've tested by creating trigger start and end time global macros and then more precisely creating those two macros at the host level. Here's my host level trigger expression:

{server1:icmpping.time()}>={$TRIGGER_START_TIME} and {server1:icmpping.time()}<={$TRIGGER_END_TIME} and {server1:icmpping.max(#3)}=0

This seems to have mixed results so I'm wondering if this is the best way to go about this?

[cbass]

I posted this a while ago but never received any feedback. So I thought I would check again to see if anyone has any suggestions on how to handle this specific situation?