How it work?
Cloud Alert uses rules to define workflow as automations. Rules map triggers to actions (or workflows), apply matching criteria, and map trigger payloads to action inputs.
- Sample event message
- Sample filter of rule criteria
Rule parameter
- Rule criteria
- Actions: There are 02 types of action upon user definition
- Slack, MS Team (ChatOps)
- Runbook
Rule criteria
Rule criteria are the rule(s) needed to be matched against (logical AND). Criteria in the rule are expressed as:
| Operator | Description |
|---|---|
| contains | Trigger value contains the provided value. Keep in mind that the trigger value can be either a string or an array (list). |
| incontains | String trigger value contains the provided value case insensitively. |
| icontains | String trigger value does not contain the provided string value case insensitively. |
| equals | Values are equal (for values of arbitrary type). |
| iequals | String trigger value equals the provided value case insensitively. |
| nequals | Values are not equal (for values of arbitrary type). |
| endswith | End of the string trigger value matches the provided string value. |
| startswith | Beginning of the string trigger value matches the provided string value. |
| istartswith | Beginning of the string trigger value matches the provided string value case insensitively. |
| exists | Key exists in payload. |
| nexists | Key doesn’t exist in payload. |
| greater_than | KTrigger value is greater than the provided value. |
| less_than | Trigger value is less than the provided value. |
| inside | Trigger payload is inside provided value. (e.g. testing if “trigger.payload in provided_value”). Reverse of contains. (where contains would test for “trigger.payload contains provided_value”). |
| ninside | Trigger payload is not inside provided value. (e.g. testing if “trigger.payload not in provided_value”). Reverse of ncontains (where contains would test for “trigger.payload does not |