Alert Management

Hi, I see that this post never got a reply, but was moved to planned for development. Though your input was noted 9 months ago, and have been used in defining and designing a notification center for our platform. Thank you very much.

As we are growing our portfolio of thresholds and monitoring capabilities there is a growing need for setting up and managing notifications. It is still in the works on how we should solve it. Even though this posted got the tag “planned for development” at some point, I would say that it is currently on our roadmap and based on the outcome of our research around how to solve it, we will plan for development accordingly.

Hello everyone. In behalf of Celanese Bishop users, we got a use case that would probably benefit from the “Filtering of alerts based on user defined logic” feature. Do you guys have an estimated date for its release?

To explain further the use case we got here:

Let’s say a timeseries should trigger an alarm if it is over 65. Our user configured the alarm accordingly, but the kept getting notifications all the time while the timeseries was over 65. He only needs the notification once, so he can get some actions done in the unit.

After this alarm, he takes action and the timeseries drops to 50. This means that everything is back to normal, and the next time it peaks to 65, he should get the alarms again. However, if the timeseries does not go below 50, he is still probably dealing with the same issue, and he should not be getting alarms, because he already knows something is happening and he is trying to fix it. There is no point on getting tons of emails while this happens.