/
Best Practice - validate anomaly alerts

Best Practice - validate anomaly alerts

The easiest and most flexible way to validate anomaly alerts, is to use the Boomi Business Rules shape. Separate rules can be created for the use cases to support, and it is easy to update and maintain.

For documentation on the alert JSON structure seen below in the screenshots, see Alerts - structure and data explained

image-20240409-084851.png
The rule above takes the Eyer - Partner Connector response message that contains information about new and updated anomaly alerts, and validates (if any) of these alerts are of “medium” or “severe” criticality. If the rule validates, the user can for instance extract the ID of the anomaly alert and continue to monitor it until it is closed.

 

image-20240409-090231.png
In the screenshot above, the Boomi Business Rules shape checks for new anomalies with severity “severe”, and that a specific metric (name) is affected.

 

 

Related content

Best Practice - configuration of the Eyer - Partner Connector
Best Practice - configuration of the Eyer - Partner Connector
More like this
Eyer Query API - current anomaly alerts
Eyer Query API - current anomaly alerts
More like this
Anomaly alert timeline explained
Anomaly alert timeline explained
More like this
Grafana - set up alerts based on anomaly alerts from Eyer
Grafana - set up alerts based on anomaly alerts from Eyer
More like this
Alerts - structure and data explained
Alerts - structure and data explained
More like this
Eyer Query API - anomaly alerts with metrics
Eyer Query API - anomaly alerts with metrics
More like this