my understanding is that when a device service encounters a fault, the icon displays in red. At this point, the ‘flag’ at the bottom right of the desktop also turns red, indicating to the administrator that there is a service fault. The administrator acknowledges the fault by setting the device to ACK, causing the flag to turn blue.
The reason for it turning blue is to signal that in case another device or service fault occurs before the previous one is resolved, the flag will turn red again to notify the administrator.
I believe my understanding is correct, right? However, when a device set as ACK returns to normal, the next time a fault occurs, the device does not turn red but directly switches to the blue ACK status. This logic seems a bit off. As there is no ‘up->acked’ action in the event notification, it prevents triggering a notification on the next fault. If a device has been previously set as ACK, it must be reset to UNACK; otherwise, the device will not turn red when a fault occurs next time. This issue has been bothering me for many years because I want to be notified via email or other means when important services encounter faults.
Does anyone know what the problem might be? Could it be a misconfiguration on my part? Thank you!
