Optionally specify the action of alert rule. This action will happen when alert rule is creating an alert. It can be omitted as null, which means that there is no action emitted when alert is created (alert is only visible in UI).
Unique identifier for each alert rule across system
Type of alert which can be mapped to human readable text in UI.
Specify all conditions which devices has to match to state alert as applicable. When device is matching the conditions, it doesn't create alert yet. But the alert rule continues to be compared against specified threshold. This is the second stage of 3 stages of rule before the alert is created.
User defined description for the alert rule which can be changed later
Pre-filter of devices which the alert will be checked against. It's used for percentage threshold of alert creation as base. The mandatory filter is organization set above. This is extended filter for example device applicationType (tizen, webos, etc.). This is the first stage of 3 stages of rule before the alert is created.
User defined name for the alert rule which can be changed later
Organizations which is checked against the rule. There can be one or more organizations. However, some alertTypes (e.g.: POLICY_VIOLATION) can be limited only to single organization.
Specify how often the rule will be checked against the current state of devices. The shorter periodicity will be, the alert rule is more costly on infrastructure. And even the shorter periodicity will be, user will be alerted in case of the same kind of alert was archived.
Specify threshold of rule. It is comparing number of devices matched the conditions above relatively against the total number devices filtered by filter above. This is the last stage of 3 stages of rule. When this rule is matched, finally the alert is created.
Generated using TypeDoc
Updates existing alert rule by it's uid. Only specified (non undefined) values are changed. The omitted values are kept as before update.