| Home Prev |  cOS Core 15.00.01 Log Reference Guide
|
Next |
|---|
All log messages have a common design with attributes that include category, severity and recommended actions. These attributes enable the easy filtering of log messages, either within cOS Core prior to sending them to a log receiver, or as part of analysis that takes place after the logging and storage of messages on an external log server.
The following information is provided for each specific log message:
The name of the log message, which is a short string, 1-6 words separated by _. Please note that the name cannot be used as a unique identification of the log message, as several log messages might share the same name.
The ID is a number made up of a string of 8 digits which uniquely identifies the log message. The first 3 digits identify the category to which the log message belongs.
![[Note]](images/note.png) |
Note |
|---|---|
|
In this guide, the Name and the ID of the log message form the title of the section describing the log message. Also note that category IDs do not always form a perfectly sequential list. There are gaps where IDs have been removed during the evolution of the software. These gaps are discussed further in an article in the Clavister Knowledge Base at the following link: |
Log messages are grouped into categories, where each category maps to a specific subsystem in cOS Core. For instance, the IPSEC category includes some hundreds of log messages, all related to IPSec VPN activities. Other examples of categories include ARP, DHCP, IGMP and USERAUTH.
In this guide, categories are listed as sections in Chapter 2, Log Message Reference.
As previously mentioned, the category is identified by the first 3 digits in the message ID. All messages in a particular category have the same first 3 digits in their ID.
The default severity level for this log message. For a list of severity levels, see section Section 1.4, Severity levels.
A brief explanation of the event that took place. This explanation often features references to parameters, enclosed in angle brackets. Example:
Administrative user <username> logged in via <authsystem>. Access level: <access_level>
|
Note |
|---|---|
| This string is only included in log messages sent to Clavister Log Receivers. |
A detailed explanation of the event.
Note that this information is only featured in this reference guide and is never actually included in the log message.
A short string, 1-3 words separated by _, of what action cOS Core will take. If the log message is purely informative, this is set to "None".
A detailed recommendation of what the administrator should do if this log message is received. If the log message is purely informative, this is set to "None".
Note that this information is only featured in this reference guide, and is never actually included in the log message.
The current revision of the log message. This is increased each time a log message is changed between two releases.
Additional Information
Depending on the log message, the following information may also be included:
The name of the parameters that are included in this log message. If a parameter is specified within square brackets (for example [username]), then the parameter is optional and may or may not be included in the log message.
The name of the context parameters that are included in this log message. See Section 1.3, Context Parameters for a description of all available context parameters.
