Resends the event that originally triggered
the event automation plan.
Before resending the event, the action modifies the event data, such
as its text and severity, to your specification.
- Requirements
- None
- Result
- The triggering event and the event that this event action generates
are both logged in the Event Log. The event that this event action
generates contains the text and event type from the original triggering
event.
- Example
- Use this event action when you want to send a secondary event
that contains information from the first event. You can change or
add to the event text. Also, you can change the event severity; for
some events, this capability is useful when you
want to increase the severity level.
For example, by default an
Topology Offline event has a severity of informational.
If you have created an event automation plan to filter
critical events and you want the Topology Offline event to be treated
as such, you can use this event action to change the severity of this
event. Create a simple filter for the Topology Offline event. Then,
use the Modify
an event and send it event
action to resend the event, but change the severity to critical in
the New event severity field. Now, the critical
event filter will catch the event and the event automation plan will perform
the prescribed action.
Note: You can use event-data-substitution
variables to include event-data information into the new event text.
For more information, see "Event-data-substitution variables." The
detail slot setting also accepts event-data-substitution variables;
however, using event-data-substitution variables in the detail slot
setting can cause errors if not done correctly.