Severity filter and message exceptions, Enabling logging to clavister loggers – Amer Networks E5Web GUI User Manual
Page 78
For backwards compatibility, cOS Core versions older than 8.90 support output to this logger but
the software itself is not included with the distribution packet since analysis of logger output is
only possible through older versions of cOS Core.
Example 2.19. Enabling Logging to Clavister Loggers
To enable logging of all events with a severity greater than or equal to Notice to the Clavister
Logger (FWLog Receiver) with IP address 195.11.22.55 listening on port 999 (the default), follow
the steps below:
Command-Line Interface
Device:/> add LogReceiver LogReceiverFWLog my_fwlog
IPAddress=195.11.22.55
Port=999
InControl
Follow the same steps used for the Web Interface below.
Web Interface
1.
Go to: System > Device > Log and Event Receivers > Add > InControl Log Receiver
(FWLog)
2.
Specify a suitable name for the event receiver, for example my_fwlog
3.
Enter 195.11.22.55 as the IP Address
4.
Click OK
The system will now be logging all events with a severity greater than or equal to Notice to the
Clavister FWLogger at 195.11.22.55.
2.2.7. Severity Filter 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 is also possible to lower or raise the severity of specific events.
The Severity Filter
The Severity Filter is a means of specifying what severities, if any, are sent to the receiver. By
default, all log messages except Debug are sent. This can be restricted further so, for example,
only Emergency, Alert and Critical messages are sent.
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
Chapter 2: Management and Maintenance
78