I am running a two node cluster and we are getting notifications for Down ended (now: Down Partial) status. Can we only trigger when status is Up (Up on both cluster members) only?
Unfortunately this isn't possible at this time. When the sensor changes status from down to something else, the condition is considered by PRTG to be cleared.
Also want to see such a feature.
Not for everyone it is clear what a (now: down partial) notification means...
I've noted your vote for this to be a feature.
This feature would be desirable!
I also have the two node cluster setup, and some application owners are getting confused when they receive their clear alerts, with one PRTG server still reporting their apps down.
Please consider adding this functionality in the future releases.
I've also noted your vote for this feature request. Thanks for posting!
Can this also be approached from a different angle?
When setting up notifications (i.e. a state trigger) - there are options for sensor state (Down, Warning, Unusual, Partial Down).
Can the clear condition be somehow linked to a state (UP) - rather than partial down?
Just a thought!
Dear A. Kupi
We have put this idea on our "wish list". We have not yet decided if we change our "clear" mechanism or not.
In general, we try to keep the number of options to the minimum. But considering the demand, we will discuss it.
I would like to tag onto this discussion as well, the partial up is confusing and would be nice as mentioned above to have the system only page when the sensor is up and not partial down.
+1 as well.
We're now giving third parties notifications for our systems and don't want to confuse them with down ended and down partials, just an explicit 100% up or down.
Yes same here. I would rather only see up/down status'. Unknowns, etc are confusing. More granular options for notifications would be great.
Hi Has there been an update on this? Specically we would like a an alarm when a start is partial down and an alarm when all our cluster nodes are up.
We see the utility of such trigger, but there is no elegant solution if we want to keep the complexity of the notification settings at a manageable level.
The cluster feature introduces a lot of ambiguity when the status of several nodes is combined. For the time being, we want to continue with the current "partial" system even though it does not cover any possible case to set a trigger. When we rework the notification and/or the cluster system, we evaluate all feature requests about this matter and decide if (and how) we can find a better way to alert by state triggers.
Just wanted to post and say we are looking for this feature as well. Very annoying.