post
https://{app-url}{}/api/v2/alerts
Create a new alert configuration
A Pro Tip:
Create an alert configuration in Anodot's UI, then retrieve it using the GET Alert by ID endpoint. You can use theconfigurationsection in the response as a starting point for creating your own alerts via API.
Request Arguments
Selected request arguments:
| Argument | Type | Description |
|---|---|---|
| timescale | string | Timescale of the alert. Valid values: {1m, 5m, 1h, 1d, 1w}. |
| type | string | Type of alert: {anomaly, static, no_data}. |
| title | string | Title displayed when the alert is triggered. |
| description | string | Description displayed when the alert is triggered. |
| search | array | Alert query. Can be defined using key/value pairs or a stream ID. To retrieve stream IDs, see GET Data Streams. |
| severity | string | Severity level of the alert: {critical, high, medium, low, info}. |
| isOnlyOpen | boolean | If enabled, notifications are sent only on alert start and alert close. |
| channels | string | IDs of channels to which the alert will be sent. See GET Channels to retrieve channel IDs. |
| subscribers | string | IDs of users who will receive the alert via email. See GET Alerts for examples with subscriber IDs. |
| conditions | array | Alert conditions. For anomaly alerts: direction, significance, and duration. For static alerts: duration and threshold. For no data alerts: no_data_duration. |
| correlatedEvents | array | Determines whether static events (from the Events API) are included. Can be filtered using key/value pairs. |
| labels | array | Labels assigned to the alert. If a specified label does not exist, it will be created. |
