Phone Lines icon GFI Support Home

Articles in this section

See more

Exinda CLI: Logging

Author: Sughra Mehdi Updated

Overview

 

This article describes the Exinda CLI command logging.

You can use the logging command to configure logging parameters and to show the system logs. You can use the show log command to view the log files. The appliance logs activities to a set of system log files.

 

Information

 

NOTE:  The following syntax convention is used:
  • {}: Options are enclosed in braces and are separated by '|'
  • []: Optional keywords are enclosed in brackets
  • <>: User input is required where variables are enclosed in greater-than and less-than symbols

 

Configuring Logging Parameters

The following table describes the commands used for configuring logging parameters:

Action Description

 Command Parameter Description
To specify when to rotate the log files logging files rotation criteria frequency {daily|weekly|monthly}

Rotate log files on a fixed schedule:

  • daily - Once per day at midnight
  • weekly - Once per week
  • monthly - On the first day of every month
logging files rotation criteria size <megabytes>

Rotate the log files when the log file surpasses a specified size threshold
logging files rotation criteria size-pct <percentage>

Rotate the logs when they surpass a specified percentage of the disk size
logging files rotation force

Force an immediate rotation of the log files

To specify the maximum number of old log files to keep

 logging files rotation max-num <number> Not Applicable 
To delete log files logging files delete {current|oldest} 
  • delete current - Delete the current active log file
  • delete oldest [<number>] - Delete one or more of the oldest log files. If deleting more than one file, specify the number of files to delete
To specify the minimum severity level of log messages saved on the local disk  logging local {none|emerg|alert|crit|err|warning|notice|info|debug}
  • none - Disable logging
  • emerg - Emergency: system is unstable
  • alert - Action must be taken immediately
  • crit - Critical conditions
  • err - Error conditions
  • warning - Warning conditions
  • notice - Normal but significant conditions
  • info - Informational messages
  • debug - Debug-level messages

logging local override class <class> priority

Override log levels on a per-class basis 

To allow syslog messages to be received from remote hosts 

 logging receive  Not Applicable 
To include the number of seconds since the epoch in the logs  logging fields seconds enable

Enable the seconds field
logging fields seconds fractional-digits {1|2|3|6}

Specify the number of digits to the right of the decimal point (truncation is from the right)
logging fields seconds whole-digits {1|6|all}

Specify the number of digits the left of the decimal point (truncation is from the left)
all - Do not limit the number of digits.
To set the format of the log files  logging format {standard|welf} 
  • format standard - Use the standard format for log messages
  • welf - Use WELF format for log messages
To set the severity of log entries recorded for select CLI commands  logging level cli commands {none|emerg|alert|crit|err|warning|notice|
info|debug}
  • none - Disable logging
  • emerg - Emergency: system is unstable
  • alert - Action must be taken immediately
  • crit - Critical conditions
  • err - Error conditions
  • warning - Warning conditions
  • notice - Normal but significant conditions
  • info - Informational messages
  • debug - Debug-level messages

To send event logs to a specified server using the syslog protocol 

 logging <hostname or IPv4 address>  Not Applicable 
Set the minimum severity of log messages sent to syslog servers logging trap {none|emerg|alert|crit|err|warning|notice|info|debug}
  • none - Disable logging
  • emerg - Emergency: system is unstable
  • alert - Action must be taken immediately
  • crit - Critical conditions
  • err - Error conditions
  • warning - Warning conditions
  • notice - Normal but significant conditions
  • info - Informational messages
  • debug - Debug-level messages

 

Viewing Log Files

The following table describes the commands used for viewing log files:

Action Description Command

Parameter Description
To view the log file show log [continuous] {matching|not matching} <regex>
  • show log - Show entire log file
  • continuous - Show the log file as it gets updated
  • matching <regex> - Show event logs that match a given regular expression
  • not matching <regex> - Show event logs that do not match a given regular expression
To view a listing of archived files

show log files

 Not Applicable 
To view the contents of a log file show log files <file number> [{matching| not matching} <regex>]
  • <file number> - The number that identifies the log file
  • matching <regex> - View entries from the selected log file that matches a given regular expression
  • not matching <regex> - View entries from the selected log file that does not match a given regular expression

 

Find more CLI commands.

Back to Top

Was this article helpful?
0 out of 0 found this helpful

Related articles