2
Management
51
Filtering severity and message exceptions
For
each
log
receiver,
it
is
possible
to
impose
rules
on
what
log
message
categories
and
severities
are
sent
to
that
receiver.
It
also
possible
to
lower
or
raise
the
severity
of
specific
events.
Filtering severity
The
Severity
Filter
is
a
means
of
specifying
what
severities,
if
any,
are
sent
to
a
log
receiver.
By
default,
all
log
messages
except
those
with
a
Debug
severity
are
sent.
However,
an
administrator
may
only
want
more
important
messages
sent.
For
example,
it
might
only
be
desirable
to
send
Emergency
,
Alert
and
Critical
messages
to
a
log
server.
Example: Configuring the severity filter
In
this
example,
it
is
assumed
that
a
Syslog
server
has
already
been
configured
in
the
SEG
with
the
logical
name
My_Syslog
.
The
aim
is
to
have
only
the
log
messages
with
a
severity
of
Emergency
or
Alert
sent
to
this
server.
Device:/>
set
LogReceiver
LogReceiverSyslog
My_Syslog
Severity=Emergency,Alert
Log message exceptions
After
the
severity
filter
is
applied,
any
Log
Message
Exceptions
are
applied
to
generated
messages.
There
can
be
more
than
one
message
exception
for
a
log
receiver
and
each
consists
of
the
following:
•
Category
and
ID
This
specifies
the
log
messages
that
will
be
affected
by
the
exception.
If
the
ID
number
of
the
log
message
is
not
specified,
all
log
messages
for
the
specified
category
will
be
included.
The
ID
of
specific
log
messages
can
be
found
in
the
Log
Reference
Guide
.
•
Type
This
can
be
one
the
following:
•
Exclude
–
This
will
exclude
the
specified
log
messages
even
if
they
are
allowed
by
the
severity
filter.
•
Include
–
This
will
include
the
specified
log
messages
even
if
they
are
excluded
by
the
severity
filter.
In
addition,
the
Severity
of
the
included
message(s)
can
be
specified.
If
this
is
set
to
Default,
the
original
severity
is
used.
Otherwise,
the
severity
is
set
to
the
specified
value.
This
provides
the
ability
to
raise
(or
lower)
the
severity
of
specific
log
messages.
