Configuring Syslog Message Severity Level
You can configure the minimum severity level of messages that you want to include in syslog messages that are generated by the device. The severity levels are described in the following table.
| ● | It's strongly recommended to leave the syslog severity level at default (i.e., Notice) to prevent excessive utilization of the device's resources. Changing severity level is typically done only by AudioCodes Support for debugging. |
| ● | Upon a device restart, the syslog severity level returns to default. |
| ● | You can also configure syslog severity levels per syslog server (see Configuring Secondary Syslog Servers). |
| Severity Level (Lowest to Highest) |
Syslog String |
Description |
|---|---|---|
|
[7] Debug |
"debug" |
Debug message. |
|
[6] Info |
"info" |
An operational message. |
|
[5] Notice (default) |
"notice" |
An unusual event has occurred. |
|
[4] Warning |
"warning" |
An error that might occur if measures are not taken to prevent it. |
|
[3] Error |
"error" |
An error has been identified. |
|
[2] Critical |
"crit" |
A problem has been identified that is critical. |
|
[1] Alert |
"alert" |
A problem has been identified and an action must be taken immediately to resolve it. |
|
[0] Emergency |
"emerg" |
A panic condition (system is unstable). |
The specified severity level and all higher severity levels are included in the syslog message. For example, if you configure the parameter to Alert, the syslog includes messages with Alert severity level and messages with Emergency severity level.
When viewing syslog messages in the Web interface (see Viewing Syslog Messages), each severity level is displayed in a different color.
| ➢ | To configure the minimum message severity level to include in syslog: |
| 1. | Open the Logging Settings page (Troubleshoot menu > Troubleshoot tab > Logging folder > Logging Settings). |
| 2. | From the 'Log Severity Level' [SyslogLogLevel] drop-down list, select the severity level. |
| 3. | Click Apply. |