Events
Overview
An event links one or more triggers to one or more actions.
This allows you to combine multiple, individual measurement values to a status.
Base Parameters
Each event has the following base parameters:
| Parameter | Description |
|---|---|
| Name | Name to identify this model |
| Enabled | Indicates if the model is enabled |
| Boolean Operator | Define how the individual Triggers are connected to each other |
| Category | The associated category |
| Description | Additional description |
| Initial Status | Status which is used after initialization |
| Force Actions | If enabled, the associated Actions are executed even if the Trigger value is the same as before |
| Logging | If enabled, this item will create log entries |
| Troubleshooter | If enabled, the troubleshooter is active |
| Last Off Time | The date and time when this Event last had the status Off |
| Last On Time | The date and time when this Event last had the status On |
| Occurrences | Number of times this item has occurred |
| Pause until | If set, prevents the execution of the associated Actions until this date and time is reached |
| Sequence Number | The unique sequence ID of this item. Used for the Ember+ provider OID. |
| Severity | The associated Severity |
| Status Code | The current status code |
| Status Message | The current status message |
| Status | The current status |
The boolean operator affects the event logic.
If you choose AND, all triggers linked with this event need to be active
for the event to switch to On,
whereas only one of the triggers needs to be active when you select OR.
Triggers
You can add as many triggers to one event as you like. They are logically combined by the boolean operator set in the event.
When adding a trigger to an event, you can configure the following parameters:
The option negate negates the trigger (logical XOR):
| Trigger Status | Negated | Status in Event |
|---|---|---|
| 0 | 0 | 0 |
| 0 | 1 | 1 |
| 1 | 0 | 1 |
| 1 | 1 | 0 |
Some examples of trigger states are:
| Trigger Status | Description |
|---|---|
| No State | Trigger status is unknown |
| Off | Trigger is off (condition not matched) |
| On | Trigger is on (condition matched) |
| Failed | Trigger has failed (e.g. lost connection, internal error) |
| Initialized | Trigger has been initialized by Broadcast Suite Core, but no data has been received so far |
| Initialization failed | Trigger initialization has failed (e.g. due to missing parameters, invalid configuration) |
| Disabled | Trigger has been disabled by |
Actions
Whenever the status of an event changes, a set of actions can be executed.
You can define the execution point of each action with the Event Transition parameter:
| Event Transition | Description |
|---|---|
| Off to On | Execute action when the event changes from off to on |
| On to Off | Execute action when the event changes from on to off |
| Both | Execute action on every status change |
Actions can be sorted with drag and drop and are executed sequentially.
The top-most action (first entry in the action list) is executed first.