Alerting
Goal: Know what the Alerting window stores, and what it does not do yet.
NOTE
The Alerting window writes alert definitions into the workspace. Today nothing in OpenX reads them to send an email or a text, so an alert defined here does not fire.
Open Workspace -> Alerting.
The list
Alerts lists each alert with its status, type, name, description and node, and Edit alert, Copy alert and Delete alert. Click a status to turn the alert on or off. Filter by Node narrows the list; Add starts a new alert.
An alert
| Field | What it is |
|---|---|
| Name | Required. Up to 100 characters |
| Description | Required. Up to 1,000 characters |
| Alert Text | Required. The message the alert would send |
| Type | Email or SMS. Changing it clears the address |
| Email Address / Phone Number | Who to tell. A phone number is 10 to 15 digits, for example 15553125678 |
| Alert After | A whole number from 0 to 1,000, and a unit: seconds, minutes or hours |
| Node | The record the alert watches ("-- Select a node --"). Only kinds turned on in the workspace are offered |
Resend alerts sets how often to repeat - a fixed interval or exponential backoff - and when to stop, with a preview of the intervals. Triggers groups rules: each trigger fires when All rules must breach or Any rule may breach, and each rule has a source, an operator and a Threshold Value.
Save and Deploy
Save in this window adds the alert to your unsaved workspace changes; it is written to the workspace with your next canvas Save. Nothing waits for Deploy.
Rights
The window checks no access right of its own; the canvas Save writes the change.
Azi and agents
Alerts are not a record kind Azi or an agent proposes.
Messages you may see
| When | Message |
|---|---|
| A required field is empty | This field is required. |
| An email address | Invalid email, ex. example@host.com |
| A phone number | Invalid phone number, ex. 15553125678 |
| Alert After | Please enter a valid integer between 0 and 1000 |
Next steps
- Saving your changes -> Save, accept and Deploy