Event Rules and Actions

Event Rules

Event rules are supposed to be created to process monitoring events. The system checks records in the Monitoring Source table against the event rule. If the records match the rule, the system should start the debounce period. At the end of the debounce period, the system should re-check the Monitoring Event whether is matches the event rule.

If it matches the rule, the system should perform all actions that are created fot this event rule in the ascending order.

Event Rule form fields

Field	Mandatory	Description
Name	Y	Specify a name for the event rule.
Description	N	Type a brief description.
Active	N	Select this checkbox to enable the rule.
Type	Y	Information – does not require a response. It is used to check the state of a device or service, and to confirm the successful competion of any operation. Warning – indicates whether a service or device has reached a threshold. Exception – determines whether the established norm for a metric of a service or system component is violated .
Message count	Y	Specify the number of the event messages required to execute the current rule. The field appears when the Information type is chosen.
Message accumulation period	Y	Specify the period during which the number of event messages specified in the Message count field should be accumulated. The field appears when the Information type is chosen.
Active event count	Y	Specify the number of active events in the Monitoring Events table for the rule to work. The field appears when the Warning type is chosen.
Revalidation period	Y	Specify the time period after which the monitoring events should recheck for compliance to the rule. The field appears when the Warning or Exception type is chosen.

Actions for Event Rule

Action for Event Rule form fields

Field	Mandatory	Description
Name	Y	Specify a name of the action.
Event rule	Y	Specify the event rule to which the action is created.
Action type	Y	Choose the action type: New record creation Record update Client script execution
Table	Y	Specify the table in which the action should be performed. The field appears when the New record creation or Record update action type is chosen.
Record	Y	Specify the record which should be updated. The field appears when the Record update action type is chosen.
Template	N	Select a column and define the value you need. Available columns depend on the table specified in the Table field.
Use script	N	Select the checkbox to display the Script field. The field appears when the New record creation or Record update action type is chosen.
Script	N	Insert a script you need to use to create a record or update record values in the source table. The field appears when the Use script option is chosen or when the Client script execution action type is chosen. Use executeScript() function with the following parameters available: event – the record in the Monitoring Event (itsm_monitoring_event) table that is created by the monitoring rule with the lowest order. message – the last record in the Target Message table related to the event. record – the record that is specified in the Record field or that is created in the specfied Table. If the Client script execution type is chosen, the record returns null.
Active	N	Select this checkbox to enable the action.
Order	N	Specify the action order. Actions are performed in ascending order.

When the actions of the New record creation and Record update types are performed, in the ITSM Task Event (itsm_task_event) table, records that call actions are created. They connect the ITSM Task (itsm_task) record to the Monitoring Event (itsm_monitoring_event) record. If the binding record exists, a new one is not created.

If the record from any ITSM Task child table has related Monitoring Event records, the relevant related list is displayed on its form.

Page tree

Event Rules and Actions

Event Rules

Actions for Event Rule