Overview and statistics

When you select a rule from the list of rules, its detailed information will be displayed to the right.

In particular, you can check the rule's:

• Name and ID - the name is defined by you when you create the rule, whereas the ID is assigned automatically by the system

• State - a rule's state can be either Defined, Enabled, Disabled, or Failed to enable

• Times triggered - shows how many times this rule has been triggered, and respectively how many tasks have been launched out of it

• Execution options - allows you to fine-tune the rule execution and set constraints that fit your use case

• Scope - displays the defined scope type and involved devices

• Last execution on devices - shows details of the most recent task launched by this rule, and how the involved devices executed it

• Triggers - expand this blade to see the triggers defined for this rule and the conditions (trigger condition and general condition), if any

• Action - expand this blade to see the Groovy action script of this rule

• Tasks - expand this blade to see all tasks launched automatically by this rule. It redirects you to Executions, where the list of executions is filtered accordingly.

• Last execution on devices - This section describes the most recently triggered rule execution (in the form of a task).
  In particular, on how many devices the related task:

  • was launched to execute an action

  • is still running

  • was finished with success, warning or error

  • was canceled

To get detailed information about executions with a certain status, click the related (positive) number.

Detailed monitoring

For more fine-grained monitoring, click on all involved or on any of the subsets of devices based on their execution state.

This will bring you to Executions where the displayed list of executions will be filtered accordingly.

In our example, this list is automatically filtered by Rule ID and by the selected execution State (e.g. Running).

The filtered result displays only 1 device (device-01) with two partial executions of the Groovy script.

• The summarized execution name is therefore formed by the rule name [how it was triggered], the device name and the state (e.g. Rule demo [Manually Triggered] on device-01 is RUNNING).

• The partial execution IDs coincide with the Task ID of the task which started these executions. This task was launched automatically by the rule we are currently monitoring.

Select a partial execution from the list for even more fine-grained monitoring of this rule execution.