Introduction to Rules - Developer Documentation
Skip to content

Introduction to Rules

A rule automatically triggers events once the defined condition has been met. The rule detects the overshooting or undershooting of a defined threshold value. The rule automatically logs each deviation with an event.

You define the exact threshold value in the rule configuration.

After creating a new rule, the rules engine will use the last 3 hours of the related data for the initial analysis.

You can use a rule to change the asset state. The state of an asset is indicated with color in the asset navigation. Multiple rules can be created for a single asset. The state of this asset will display the highest severity level of the triggered rules. The asset navigation takes on the color of the asset state with the highest severity.

Deleted assets and rules

If you delete an asset the rule will also be deleted. Deleting the rule can take up to half an hour after the asset has been deleted.

Note

The rule engine triggers only in case of state changes. If values are still violated the rules are not triggered again. For Example: A rule has been created to monitor a value greater 90. Now the value changes from 89 to 91 - means a state change happens - and the rule will be triggered and perform the configured actions. Next the value changes from 91 to 100 - here no state change happens, due to the rule is already violated - and the rule won't be triggered again.

Note

  • For Insights Hub value plan subscribers, the number of rules that can be configured is limited as per the package.
  • For Insights Hub capability packs subscribers, rules can be added as required. Rules consumption above the limit in the subscribed package will be charged separately.

Rules on 'Insights Hub Start for Free' accounts

  • Rules are running only for 24 hours. After that they are disabled automatically. A user can enable it again if needed for further 24 hours.

Last update: January 22, 2024