The repeated sending of notifications can be defined by two ways:
v The snooze parameter causes the notifications to be sent again and again to the
same destinations. The time in minutes between the repeated transmissions is
determined by the snooze value.
v The escalation_time and escalation_rule parameters causes the notifications to
be sent to the destination list of the escalation_rule if it is not cleared within
escalation_time minutes.
Rules can escalate only to alerting rules (meaning to rules that have snooze or
escalation definitions) in order to prevent a situation where notifications are
stopped from being sent.
A rule cannot escalate to itself, and neither can it be defined in a cyclic escalation
of rules.
escalation_only defines a rule without filters, which can only be used as an
escalation for other rules.
The snooze time cannot be longer than the escalation time.
It is not permitted to define new rules while there are uncleared alerting events.
The following example sends alerts upon critical events to John's cellular number
and to the emails of all the IT staff. The alerts will be resent every 20 minutes until
the events are cleared.
Example:
xcli -u -c Nextra1 rule_create rule=critical_alerts min_severity=critical
destinations=john-cell,itstaff snooze_time=20
Output:
Command executed successfully.
Access Control:
User Category Permission
Storage administrator Allowed
Storage integration administrator Disallowed
Application administrator Disallowed
Security administrator Disallowed
Read-only users Disallowed
Technicians Disallowed
Completion Codes:
v CANNOT_CHANGE_EVENT_CONF_WITH_ALERTING_EVENTS
Cannot change event configuration while there are alerting events
Troubleshooting: Clear all alerting events before changing event configuration
v EVENT_RULE_MAX_REACHED
Maximum number of event rules already defined
288 IBM XIV Storage System User Manual
To Next Page
Loading...
Need help?
General
