# Set up custom metrics monitoring
URL: https://docs.datarobot.com/en/docs/workbench/nxt-console/nxt-settings/nxt-custom-metrics-settings.html

> Enable custom metrics monitoring by defining the 

# Set up custom metrics monitoring

On a deployment's Settings > Custom metrics tab, you can define "at risk" and "failing" thresholds to monitor the status of the custom metrics you created on the [Custom metrics](https://docs.datarobot.com/en/docs/workbench/nxt-console/nxt-monitoring/nxt-custom-metrics.html) tab.

On a deployment's Custom Metrics Settings page, you can configure the following settings:

| Field | Description |
| --- | --- |
| Association ID |  |
| Association ID | Defines the name of the column that contains the association ID in the prediction dataset for your model. Association IDs function as an identifier for your prediction dataset so you can later match up outcome data (also called "actuals") with those predictions. |
| Require association ID in prediction requests | Requires your prediction dataset to have a column name that matches the name you entered in the Association ID field. When enabled, you will get an error if the column is missing. This cannot be enabled with Enable automatic association ID generation for prediction rows. |
| Enable automatic association ID generation for prediction rows | With an association ID column name defined, allows DataRobot to automatically populate the association ID values. This cannot be enabled with Require association ID in prediction requests. |
| Enable automatic actuals feedback for time series models | For time series deployments that have indicated an association ID. Enables the automatic submission of actuals, so that you do not need to submit them manually via the UI or API. Once enabled, actuals can be extracted from the data used to generate predictions. As each prediction request is sent, DataRobot can extract an actual value for a given date. This is because when you send prediction rows to forecast, historical data is included. This historical data serves as the actual values for the previous prediction request. |
| Segmented analysis |  |
| Track attributes for segmented analysis of training data and predictions | Enables DataRobot to monitor deployment predictions by segment, for example by categorical features. For more information, see the segmented analysis settings documentation. |
| Definition |  |
| At Risk / Failing | Enables DataRobot to apply logical statements to calculated custom metric values. You can define threshold statements for a custom metric to categorize the deployment as "at risk" or "failing" if either statement evaluates to true. |

## Define custom metric monitoring

Configure thresholds to alert you when a deployed model is "at risk" or "failing" to meet the standards you set for the selected custom metric.

> [!NOTE] Note
> To access the settings in the Definition section, configure and save a metric on the [Custom Metrics](https://docs.datarobot.com/en/docs/workbench/nxt-console/nxt-monitoring/nxt-custom-metrics.html) tab. Only deployment Owners can modify custom metric monitoring settings; however, Users can [configure the conditions under which notifications are sent to them](https://docs.datarobot.com/en/docs/workbench/nxt-console/nxt-settings/nxt-notification-settings.html).Consumers cannot modify monitoring or notification settings.

You can customize the rules used to calculate the custom metrics status for your deployment on the Custom Metrics Settings page:

1. In a deployment you want to monitor custom metrics for, clickSettings > Custom metrics.
2. In theDefinitionsection, define logical statements for any of your custom metrics'At RiskandFailingthresholds: SettingDescriptionMetricSelect the custom metric to add a threshold definition for.CategoryFor a categorical custom metric, select which category (i.e., class) in the metric to add a threshold definition for.ConditionSelect one of the following condition statements to set the custom metric's threshold forAt RiskorFailing:is less thanis less than or equal tois greater thanis greater than or equal toValueEnter a numeric value to set the custom metric's threshold forAt RiskorFailing. For example, a statement could be: "The ad campaign isAt Riskif theCampaign ROIisless than10000." Remove a ruleTo remove a rule, click the delete iconnext to that rule.
3. After adding custom metrics monitoring definitions, clickSave.

---
