Database Reference
In-Depth Information
Save as Alert screen showing other options
11. Select
List in Triggered Alerts
, and, under
Severity
,
High
. Notice that you
could also send an e-mail or run a script. If you choose to run a script, you could
design it to take actions like shutting down the system, disallowing any more at-
tempts at user log in, and other steps. Running a script is often used to curtail fur-
ther access or to prevent problems until the system is fixed.
12. Click under
When triggered
|
execute action
|
Once
.
13. Notice that there is an option to
Throttle
. If you check the
Throttle
box, an area
opens that asks you how long after executing actions to suppress alerts for. You
can choose a number and a period of time (seconds, minutes, hours, or days).
Throttling prevents the announcement of more alerts until a specified time after
the first alert is issued. When you set a time for throttling, it needs to be based on
the specifics involved. You wouldn't want to set it so that a crucial alert would be
prevented, but you also don't need to see every alert go off once you know there is
a problem. There is a fine balance to strike in order to set the throttling for the
right amount of time. Here, however, we are not concerned about throttling and
leave the box unchecked.
