We have remote probes running on many systems worldwide. These are deployed on devices that may loose internet connection from time to time. This does however not mean the probe server is in bad shape. Only that the internet connection is.
We have made a map for survaillance and setup an email service to alarm us on errors on the remote probe systems. This works well in general. What we miss, is the opportunity to disregard the "Disconnected" alarms the remote probes generate. It's fine that they show up read with the small "X" on the icon on the map, but they also go into the alarm list and may stay there for many days/months. This can cause technicians to overlook other important alarms on connected systems. Setting them into pause could be an idea, but this means we manually have to discover that they reconnected which doesn't seem like the right solution.
Can we somehow make a setting causing the disconnection of remote probes not to be treated as alarms?
Kind regards Kenneth Vindum FLSmidth