Event Rules

Event rules are used to process monitoring events. The system checks records in the Monitoring Event table against the event rule. If the records match the rule, the system starts counting down the revalidation period. At the end of this period, the system rechecks whether the Monitoring Event records match the event rule.

There is no revalidation period for the Information event type.

To create an event rule, complete the following steps:

  1. Navigate to Monitoring and Event Management → Configuration → Event Rules.
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to apply the changes.

Event Rule form fields

FieldMandatoryDescription
NameYSpecify a name for the event rule. The name should be unique.
DescriptionNType a brief description.
ActiveNSelect this checkbox to enable the rule.
TypeY

Specify the event type. Available options:

  • Information – responds to a sequence of informational messages associated with non-critical events. For example, consecutive errors occurred during the user authentication in a short time. 
  • Warning – indicates whether one of the service or device parameters has reached a threshold value.
  • Exception – determines whether a metric for a service or a system component has reached a specified breach value.
Message countY

Specify the number of the event messages required to execute the current rule. 

The field appears when the Information type is chosen.


Message accumulation periodY

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 countY

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 periodY

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.


Action for Event Rule

When the event records are rechecked, and they still match the rule, the system performs all actions created for this event rule in ascending order. 

To create actions, complete the following steps:

  1. Open the event rule record for which you need to create an action.
  2. Navigate to the Related Lists area, select the Action for Event Rule tab.
  3. Click New and fill in the fields.
  4. Click Save or Save and Exit to apply the changes.

You can also open the action form via the Navigator menu. To do this, navigate to Monitoring and Event Management → Configuration → Action for Event Rules and click New. In this case, you need to fill in the Event rule field manually. 


Action for Event Rule form fields

FieldMandatoryDescription
NameYSpecify a name of the action.
Event ruleY

Specify the event rule for which the action is created. 

Action typeY

Choose the action type:

  • New record creation
  • Record update
  • Client script execution
TableY

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.


RecordY

Specify the record which should be updated. 

The field appears when the Record update action type is chosen.


TemplateN

Select a column and define the value you need. Available columns depend on the table specified in the Table field.

The field appears when the New record creation or Record update action type is chosen.


Use scriptN

Select the checkbox to display the Script field.

The field appears when the New record creation or Record update action type is chosen.


ScriptN

Enter a script using the SimpleOne Server-Side API. 

The field appears when the Use script option is chosen or when the Client script execution action type is chosen.

Use the executeScript() function with the following parameters, which are SimpleRecord objects:

  • event – the record in the Monitoring Event (itsm_monitoring_event) table that is created by the monitoring rule with the lowest order and is related to the current event rule.
  • message – the last record in the Target Message table related to the event.
  • record – the record that is specified in the Record field or created in the specified Table. If the Client script execution type is chosen, the record is null.  
ActiveNSelect this checkbox to enable the action.
OrderNSpecify 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.

Message processing

After setting up all the necessary elements (monitoring source, event rules and actions, adding a system user with the monitoring_message_creator role), the system is ready to receive messages from the monitoring systems. When messages are received, SimpleOne analyzes them and, if necessary, performs the specified actions. For example, the system creates an infrastructure incident, updates the operational status of a CI.