EasyManua.ls Logo

Fortinet FortiRecorder 100D - Viewing log messages

Fortinet FortiRecorder 100D
169 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
System monitoring Page 93 FortiRecorder 2.4.2 Administration Guide
Log severity levels
Each log message contains a Severity (pri) field that indicates the severity of the event that
caused the log message, such as pri=warning.
For each location where the FortiRecorder appliance can store log files (disk, Syslog or
FortiAnalyzer), you can define a severity threshold. The FortiRecorder appliance will store all log
messages equal to or exceeding the log severity level you select.
For example, if you select Error, the FortiRecorder appliance will store log messages whose log
severity level is Error, Critical, Alert, and Emergency.
Viewing log messages
You can use the web UI to view and download locally stored log messages. (You cannot use the
web UI to view log messages that are stored remotely on Syslog or FortiAnalyzer devices.) Log
messages are in human-readable format, where each log field’s name, such as Message (msg
field when viewing a raw, downloaded log file), indicates its contents.
To view log messages
1. Go to either Monitor > Log Viewer > Event (to view event logs about the appliance itself) or
Monitor > Log Viewer > Camera (to view logs about connected cameras).
Columns and appearance varies slightly by the log type.
Initially, the page displays a list of log files of that type.
2. Double-click the row of a log file to view the log messages that it contains.
Table 10:Log severity levels
Level
(0 is greatest)
Name Description
0 Emergency The system has become unusable.
1 Alert Immediate action is required.
2 Critical Functionality is affected.
3 Error An error condition exists and functionality could be
affected.
4 Warning Functionality could be affected.
5 Notification Information about normal events.
6 Information General information about system operations.
Avoid recording log messages using low log severity thresholds such as information or
notification to the local hard disk for an extended period of time. A low log severity threshold is
one possible cause of frequent logging. Excessive logging frequency can cause undue wear on
the hard disk and may cause premature failure.

Table of Contents

Related product manuals