# BasicAlertConfig
**Source definition:** [`src/bitdrift/public/unary/alerts/v1/alerts.proto#L27-L58`]()
An alert definition global for an individual metric aggregated ID. This is shared across N
workflows/charts if all of those workflows/charts refer to the same aggregated ID.
| Field | Type | Description |
|---|---|---|
| threshold | double | The threshold value for the alert that will cause the alert to trigger. |
| condition | [bitdrift.public.unary.alerts.v1.ThresholdCondition](bitdrift_public_unary_alerts_v1_ThresholdCondition.md "bitdrift.public.unary.alerts.v1.ThresholdCondition")
must be a defined enum value | The condition that the threshold must meet for the alert to trigger. |
| window | [google.protobuf.Duration](https://protobuf.dev/reference/protobuf/google.protobuf/#duration "google.protobuf.Duration") | The window over which the alert will be evaluated. Currently supported windows include: 5 minutes, 1 hour, and 1 day. Regardless of the window, alerts are currently evaluated every 5 minutes. |
| consecutive_data_points | optional uint32 | The number of consecutive data points that must meet the threshold condition for the alert to trigger. The aggregation window of each point depends on the evaluation window. For 5 minute and 1 hour evaluation windows, the aggregation window is 1 minute. For the 24 hour evaluation window, the aggregation window is 15 minutes. If not set defaults to 1. |
| histogram_configuration | [bitdrift.public.unary.charts.v1.HistogramConfiguration](bitdrift_public_unary_charts_v1_HistogramConfiguration.md "bitdrift.public.unary.charts.v1.HistogramConfiguration") | Configuration for any histogram values within the aggregate ID. This is required if the aggregate ID refers to a histogram so that one or more percentiles can be used as part of the alert condition. |
| limit_strategy | [bitdrift.public.unary.charts.v1.LimitStrategy](bitdrift_public_unary_charts_v1_LimitStrategy.md "bitdrift.public.unary.charts.v1.LimitStrategy") | Optional limit strategy to use for this alert. If this is omitted, a default value of limiting by a top k of 5 entries is used. Ultimately this will allow alerting on specific dimensions for a group by aggregate ID if desired. |
| unique_device_threshold | optional uint32 | If specified, the alert will only trigger if at least this many unique devices are present in each consecutive data point that breaches the threshold condition. |
Example
```json
{
"condition": "ABOVE",
"consecutive_data_points": 3,
"histogram_configuration": {
"percentile": 1.0,
"percentiles": [
1.0
]
},
"limit_strategy": {
"exclusions": {
"dimension_identifiers": [
{
"id": "time_series_id_opaque_example",
"labels": [
{
"name": "name",
"value": "value"
}
]
}
],
"return_other": false
},
"sort_order": "MAX",
"top_k_limit": {
"top_k": 5
}
},
"threshold": 0.75,
"unique_device_threshold": 50,
"window": "3600s"
}
```