Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Event Rules
Event rules are supposed 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 should start starts counting down the debounce revalidation period. At the end of the debounce this period, the system should re-check rechecks whether the Monitoring Event records , whether they match the event rule or not.
| Info |
|---|
There is no revalidation period for the Information event type. |
To create an event rule, complete the following steps:
- Navigate to Monitoring and Event Management → Configuration → Event Rules.
- Click New and fill in the fields.
- Click Save or Save and Exit to apply the changes.
Event Rule form fields
| Field | Mandatory | Description | ||
|---|---|---|---|---|
| Name | Y | Specify a name for the event rule. The name should be unique. | ||
| Description | N | Type a brief description. | ||
| Active | N | Select this checkbox to enable the rule. | ||
| Type | Y | Specify the event type. Available options:
| ||
| Message count | Y | Specify the number of the event messages required to execute the current rule.
| ||
| Message accumulation period | Y | Specify the period during which the number of event messages specified in the Message count field should be accumulated.
| ||
| Active event count | Y | Specify the number of active events in the Monitoring Events table for the rule to work.
| ||
| Revalidation period | Y | Specify the time period after which the monitoring events should recheck for compliance to the rule.
|
Action for Event Rule
When the event records are re-checkedrechecked, and they still match the rule, the system performs all actions that are created for this event rule in the ascending order.
To create actions, complete the following steps:
- Open the event rule record to for which you need to create an action.
- Navigate to the Related Lists area, click the select the Action for Event Rule tab.
- Click New and fill in the fields.
- Click Save or Save and Exit to apply the changes.
| Info |
|---|
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
| Field | Mandatory | Description | ||
|---|---|---|---|---|
| Name | Y | Specify a name of the action. | ||
| Event rule | Y | Specify the event rule tofor which the action is created. | ||
| Action type | Y | Choose the action type:
| ||
| Table | Y | Specify the table in which the action should be performed.
| ||
| Record | Y | Specify the record which should be updated.
| ||
| 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.
| ||
| Script | N | Insert Enter a script you need to use to create a record or update record values in the source table. using the SimpleOne Server-Side API.
Use the executeScript() function with the following parameters available, which are SimpleRecord objects:
| ||
| 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.
| Info |
|---|
If the record from any ITSM Task child table has related Monitoring Event records, the relevant related list is displayed on its form. |
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|