The ORD scheme is similar to the query string of a URL, where parameters follow a colon, name and values are joined with an equal character, and pairs are separated with an ampersand character. For example:
slot:/|alerts:The ORD you use in the bound table needs to be in the same scope as your alert is configured. If you have alerts configured to run on a hierarchy, configure something like this for the ORD in the table binding:
hierarchy:/AnalyticDataModel|alerts:You would not use both examples simultaneously.
| Column | Description |
|---|---|
| alert | The ORD to the active alert. |
| node | The ORD to the node on which there is an alert. |
| state | Alert or Normal. |
| totalCost | The cost of the alert multiplied by the corresponding alert mode. |