Alerts & Integrations
Once you've set your monitors, learn how to decipher their status and set up an alerting system.
Monitors are continuously evaluated according to each monitor's configurations -- an evaluation will result in one of the following statuses for a monitor, ordered by severity:
When viewing the health of your model for a monitor type (drift, performance, or data quality), the status shown will be based on the highest severity of any of the model's monitors for that type. For example, if you are monitoring your model with several performance monitors, such as Accuracy and F1-score, and at least one of them has a "Triggered" status, the status shown for the model's performance will be "Triggered".
No action is needed!
This shows when the monitor does not have recent data in the evaluation window. This can be resolved by extending the evaluation window or uploading new data to Arize. All live models should be configured to continuously send your model’s latest data in batch or real-time operations to keep monitors up-to-date.
The Arize platform offers drift and performance troubleshooting to root cause model issues and pinpoint specific feature values or cohorts of data where the model performing poorly.
Once you set up your monitors, you’ll want to be alerted when your model deviates from its expected ranges.
Arize offers alerting integrations for alerting tools and methods. Send an alert via email, slack, OpsGenie, and PagerDuty. Within these tools, you can add configurations to edit your alerting cadence, severity, and alert grouping.