Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.

Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |

Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Event Processing
Time-Based Event Automation
Time-based event automation rules enable administrators to configure actions to be executed on events matching a user-defined set of criteria after a specified time.
Automating the execution of actions on events results in increased operator efficiency and usability. With time-based event automation, many recurring tasks can be automated, leaving operators more time to work on the important task.

Administration > Event Processing > Automation > Time-Based Event Automation
Alternatively, click Time-Based Event Automation.
Learn More

Time-based event automation rules can be very helpful in the following situations:
-
If an automatic action for a message fails, you can configure a restart of the automatic action after a short delay. If it repeatedly fails, after a predefined number of retries, further retries are stopped and the event is escalated.
-
If an event is not being worked on after a predefined period in time, you can configure a change to give it higher priority, for example by increasing its severity, or be assigned to a more expert group.
-
You can configure the closing of an event that is older than a predefined period of time.
If you expect duplicates of an event to arrive, you can configure the closing of the event based on the time received of the last duplicate event.
-
You can configure transferring control for events based on time. For example, escalate if an event remains in browser for longer than 2 days, close if message remains for longer than 7 days (despite the escalation after 2 days).
Note TBEA does not take closed events into account. In general, event forwarding rules are the only type of event automation rule that can be configured to take closed events into account. For more information on event forwarding, see Event Forwarding.

Each time-based event automation rule consists of three main elements:
-
Filter defining the events to which time-based event automation rules are to be applied.
-
Time period defining the duration an event has to continuously match the rule's filter to execute the rule's actions on that event.
-
List of actions to be executed on matching events. Available actions are re-running automatic actions on events, modifying event attributes, forwarding events to external servers, assigning events to users and groups, executing scripts, and executing Run Books.

Time-based automation rules are active immediately after activation.
When a new event arrives, the conditions of the rule are immediately evaluated: does the event match the filter criteria of the event filter for the time period specified by the match time? If yes, the configured actions are executed after the match period has elapsed.
For existing events, the rule conditions are only evaluated when an event changes. Therefore, to apply time-based automation rules to existing events, you must first change the events in such a way that they match the event filter for the specified match period.
Time-based automation rules are not re-applied if a matching event still matches the rule condition after that rule has been executed. To start another time-based automation rule execution, an event must first change in such a way that it no longer matches the rule condition and later change so that it matches again.
Only the transition from not-matching or new, to matching a rule condition triggers a rule re-execution. For example, you set a rule to execute an action an hour after an event’s auto-action state becomes SUCCEEDED
. An event arrives with the SUCCEEDED
auto-action state, and the rule is triggered after an hour. The event’s auto-action state will switch from SUCCEEDED
to RUNNING
until the action is finished and the state changes back to SUCCEEDED
. The change to a SUCCEEDED
state will trigger another run of the rule after an hour. This process could loop indefinitely, unless you set the number of execution attempts.

The following time-based automation rules are provided with OMi. These are disabled by default.
-
Close Old Events — Sets lifecycle state of all not closed events older than one week to closed.
-
Forward To Trouble Ticket System — Forwards all unresolved events older than one day to the trouble ticket system.
Note The system is specified as an alias server. Configure the Trouble Ticket Server alias server to connect to the physical trouble ticket server system. For details, see How to create and associate an alias to a connected server.
-
Increase Severity And Priority — Increments the severity and priority by one of all events that have been in lifecycle state open for longer than one hour.
-
Restart Failed Automatic Action — Restarts any failed automatic action after a delay of 1 minute, with a maximum of 3 retries.
Tasks

-
In the Time-Based Automation Rules pane, click the
New Item button to open the Create New Time-Based Automation Rule dialog box.
-
Enter a Display Name and optionally a Description for the rule being specified.
-
Select an event filter for the rule from the Event Filter list. The filter determines which events to consider in the rule.
If no appropriate filter is already configured, click the Browse (...) button, which opens the Select an Event Filter dialog box. Create a filter or edit an existing one. For information about filters, see Event Filters.
Note Make sure that the selected event filter does not contain any time-based filter criteria. In time-based event automation rules, the match period determines the timing.
-
Set the match period for the rule. The specified actions are executed on the event if the rule remains matched for the specified time period after the event started matching the rule's filter.
-
Optional. Limit the number of executions for a specific rule on the same event. This changes the default execution number which is indefinite.
-
Optional. Click Reset schedule on duplicate event to restart the match period when a duplicate event arrives.
By default, the arrival of duplicate events does not impact the match period. For example, a rule could close an open event after 30 days, even though duplicates of the event arrive after 29 days and indicate that the problem persists. The Reset schedule on duplicate event option resets the match period to start again when a duplicate event has been received.
-
Optional. Clear Activate rule after creation, if you do not want the rule to be active immediately.
By default, a duplicated time-based event automation rule is active immediately after creation.
-
Click Next to open the Actions page.
-
Specify the actions that you want to include in this rule as follows:
-
Click the
New Item button and select an action.
-
Enter the required information in the associated dialog box. For further information on specifying actions, see How to specify actions for time-based event automation rules.
-
Repeat for all other actions that you want to specify.
-
-
If necessary, change the order of action execution for the rule using the
Move Up and
Move Down buttons.

-
Open the Actions page of the Time-Based Event Automation Rules manager. For detailed instructions, see How to create a time-based event automation rule.
-
Click the
New Item button and select an action.
The associated dialog box opens.
-
Enter the required information in the associated dialog box. The following sections provide further information on specifying the available actions:
Re-running automatic actions
If you want the automatic action associated with a matching event to run as part of the time-based event automation rule being configured, click the
New Item button and select Re-run Automatic Action to include Re-run automatic action in the Actions list.
Modifying events and custom attributes
If you want to modify event attributes and custom attributes for matching events, click
New Item and select Modify Event to open the Modify Event Attributes dialog box and specify attributes and custom attributes as described in the following procedure.
If you want to modify event attributes for matching events, complete steps a to c. Otherwise, go to step d.
-
To modify an event attribute, click
New Item from the Attributes table menu and select an attribute from the list.
The Create New Event Attribute Modification dialog box opens appropriate for the selected attribute.
-
Specify how the attribute is to be changed when the time-based event automation rule is executed and click OK.
-
Repeat steps a and b for all other attributes that should be modified by this rule.
If you want to modify custom attributes for matching events, complete steps e to g. Otherwise, go to step h.
-
To modify a custom attribute, click
New Item from the Custom Attributes table menu.
The Create New Event Attribute Modification dialog box opens.
-
Enter the value that the custom attribute should take when the time-based event automation rule is executed and click OK.
-
Repeat steps e and f for all other custom attributes that should be modified by this rule.
Forwarding events
If you want to forward matching events, click
New Item and select Forward Event to open the Forward Event dialog box. Specify the forwarding rule as follows:
-
Select the Target Server to which you want to forward the event. This is the name of connected server name to which events are forwarded.
-
Select the Forwarding Type. The options include:
-
Notify — Target server receives original events but no further updates
-
Notify and Update — Target server receives original events and all further updates
-
Synchronize — Target server receives original events and all further updates and sends back all updates
-
Synchronize and Transfer Control — Target server receives original events and updates and sends back all updates. Ownership of the event is transferred to the other server.
This option is available only if Enable synchronize and transfer control is enabled on the selected connected server.
-
Note For a TBEA rule that was created with the understanding that the associated connected server has the
Synchronize and Transfer Control
forwarding type enabled, and the connected server configuration is later changed to disableSynchronize and Transfer Control
, theSynchronize
forwarding type is used.TBEA rules are not automatically modified when connected server configurations are changed.
Assigning events to users and groups
If you want to assign events to users or groups on matching events, click
New Item and select Assign Event to open the Assignment dialog box and specify how events are to be assigned to users or groups as follows:
-
Select a User Group.
-
Select a User.
Note Leaving user or group empty clears that assignment.
<unknown>
is displayed if the user or group is not available. If<unknown>
is displayed, select an available user or group.Running scripts
If you want to run scripts defined using the Managing Scripts dialog box on matching events, click
New Item and select Run Script to open the Run Script dialog box and specify the Event Processing Script that should be run from the list and click OK.
Note Time-based event automation scripts can only be deleted if they are not referenced in any time-based event automation rule.
To create and edit scripts, open the Event Automation Configuration dialog box, using the Manage Scripts link. For information about defining scripts, see Event Automation Scripts.
Running Run Books
If you want to run Run Books on matching events, click
New Item and select Launch Run Books to open the Run Books dialog box.
Specify the Run Books that should be run for the selected CI types as follows:
-
Click
New Item from the Run Books dialog box.
The Select Run Books dialog box opens.
-
Select a CI type from the Select a CI Type pane. The CI type is mapped to a Run Book in the Run Book automation rule.
-
Select a Run Book mapping for the selected CI type and click OK.
The new Run Book automation mapping is added to the list of selected Run Books.
-
Repeat steps b and c for all other Run Books that you want to configure.
-
In the Run Books dialog box, click OK.
-

-
In the Time-Based Automation Rules pane, select the time-based event automation rules that you want to enable or disable.
-
Click
Activate Item to enable the selected rules or
Deactivate Item to disable the selected rules.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: