Notification —
139
2.
Type
: Determine what action the filter should take: redirect, acknowledge, suspend, or supplement
the incoming notification.
3.
Send to
: The
Redirect Notification
and
Supplemental Notification
options in step two require an
email address to which to send the notifications. The remaining options require no email address.
4.
Scope
: Determine which monitoring components are subject to the filter.
5.
Organization/Scout/Probe
: This option allows you to select the organization, scout(s), or probe(s) to
which this filter applies. To select multiple items from the list, hold the
Ctrl
key while clicking the
names of the items. To select a range of items, hold the
Shift
key while clicking on the first and
last items in the range.
6.
Probes in State
: Select which probe state(s) relate to the filter. For example, you may choose to
create a supplemental notification for critical probes only. Un-check the box to the left of any state
you want the filter to ignore.
7.
Notifications sent to
: This is the method to which the notification would be sent if no filter were in
place. You may, for example, redirect notifications that would normally go to a user should that
individual go on vacation, leaving all other notifications from the probe unchanged.
8.
Match Output
: Select precise notification results by entering a regular expression here. If the
"Message:" portion of the notification does not match the regular expression, the filter is not applied.
9.
Recurring
: Select whether a filter runs continuously or on a recurring basis. A recurring filter runs
multiple times for a period of time smaller than the duration of the filter. For example, a recurring
filter could run for 10 minutes of every hour between the start and end times of the filter. A non-
recurring filter runs continuously between the start and end times of the filter.
10.
Beginning
: Enter a date and time for the filter to begin operation.
11.
Ending
: Enter an end date and time for the filter.
12.
Recurring Duration
: How long a recurring filter instance is active. This field, applicable to recurring
filters only, begins at the
Beginning
time specified above. Any notification generated outside of the
specified duration is not filtered.
13.
Recurring Frequency
: How often the filter activates.
Notification filters cannot be deleted. However, a filter may be canceled by setting the end date to
some time in the past. (Note that the end date must be equal to or later than the start date, or the
change fails.) Another method is to select a set of filters from the
Active
page and click the
Expire
Notification Filters
button in the lower right. These filters are then canceled and appears in the
Expired Filters
tab.
6.10.2.1.2. Notification � Notification Filters � Expired Filters
This tab lists all notification filters whose end date has passed. Expired filters are stored indefinitely;
this allows an organization to recycle useful filters as needed and provides a historical record for
troubleshooting.
Содержание NETWORK SATELLITE 5.1.1 - RELEASE NOTES
Страница 1: ...Red Hat Network Satellite 5 1 1 Reference Guide Red Hat Network Satellite ...
Страница 10: ...x ...
Страница 30: ...Chapter 2 Red Hat Update Agent 18 Figure 2 11 Available Package Updates ...
Страница 46: ...34 ...
Страница 68: ...56 ...
Страница 162: ...150 ...
Страница 174: ...162 ...
Страница 186: ...174 ...
Страница 259: ...247 Appendix D Revision History Revision History Revision 1 0 ...
Страница 260: ...248 ...
Страница 268: ...256 ...