Monitoring: Threshold alerts should have more options

Thank you for your valuable feedback!

We appreciate your effort. Kindly ensure all necessary details are provided. Stay tuned for updates on the progress of your submission. Feel free to reach out if you have any additional information to share.

Thanks a lot for the great feedback with respect to this. We are currently working on adding the in between thresholds functionality and have the outside range one in the roadmap for the months to come. What other models would be potentially useful in this regard ?

I’m sure having the ability to create more logic to establish a threshold would be useful - rather than having to build a synthetic calculated time series within SDK and then setting up a simple monitoring job based on current basic threshold features. Not all users have the understanding of SDK and would rather this be brought forward into Monitoring jobs.

This item was discussed internally with Ram and it was agreed this is a high priority for Celanese

I’m having a similar issue where we need to have multiple conditions for an alert to be created.

E.g. I want an alert to be triggered in the below scenario:

• When Timeseries Tag A is less than x AND when Timeseries Tag B is greater than y

This would be far easier than having to create synthetic calculated time series tags for each alert that requires multiple conditions (as above example). We are currently setting up charts and monitoring jobs and could have 100’s of scenarios like this.

​@Arun Arunachalam can you please suggest if this is being looked at and provide a timeline for availability in Production? Thanks