Chapter 13 Logging and Reporting : Logging and reporting overview : Log messages : Explanation of a debug log message
  
Explanation of a debug log message
Debug log messages are only generated if the log severity level is set to Debug. The Debug severity level is the lowest log severity level and is rarely used. This severity level usually contains some firmware status information that is useful when the FortiGate unit is not functioning properly. Debug log messages are generated by all types of FortiGate features.
The following is an example of a debug log message:
date=2010-01-25 time=17:25:54 logid=9300000000 type=utm subtype=webfilter eventtype=urlfilter level=debug msg=“found in cache”
 
Table 81: Example of a Debug log message
Debug log
date=(2010-01-25)
The year, month and day of when the event occurred in the format yyyy-mm-dd.
time=(17:25:54)
The hour, minute and second of when the event occurred in the format hh:mm:ss.
logid=(93000000000)
A ten-digit unique identification number. The number represents that log message and is unique to that log message. This ten-digit number helps to identify the log message.
type=(utm)
The section of system where the event occurred.
subtype=(webfilter)
The subtype of the log message, the UTM profile in a UTM log message.
eventtype=(urlfilter)
The event type of the log message. This represents a policy applied to the FortiGate feature in the firewall policy.
level=(debug)
The priority level of the event. There are six priority levels to specify.
msg=(“found in cache”)
Explains the activity or event that the FortiGate unit recorded.
msg=(“found in cache”)
Explains the activity or event that the FortiGate unit recorded.