Using Logs for Troubleshooting
Description — Couchbase Lite on Swift — Using Logs for Troubleshooting
Related Content — Troubleshooting Queries | Decoding Crash Logs
|
Constraints
|
Introduction
Couchbase Lite provides a robust Logging API [1] — see: API References for Log, FileLogger and LogFileConfiguration — which make debugging and troubleshooting easier during development and in production. It delivers flexibility in terms of how logs are generated and retained, whilst also maintaining the level of logging required by Couchbase Support for investigation of issues.
Log output is split into the following streams:
-
Here logs are written to separate log files filtered by log level, with each log level supporting individual retention policies.
-
You can independently configure and control console logs, which provides a convenient method of accessing diagnostic information during debugging scenarios. With console logging, you can fine-tune diagnostic output to suit specific debug scenarios, without interfering with any logging required by Couchbase Support for the investigation of issues.
-
For greater flexibility you can implement a custom logging class using the Logger interface.
In all instances, you control what is logged and at what level using the Log class.
Console based logging
Console based logging is often used to facilitate troubleshooting during development.
Console logs are your go-to resource for diagnostic information. You can easily fine-tune their diagnostic content to meet the needs of a particular debugging scenario, perhaps by increasing the verbosity and-or choosing to focus on messages from a specific domain; to better focus on the problem area.
Changes to console logging are independent of file logging, so you can make change without compromising any files logging streams. It is enabled by default. To change default settings use database’s Log method to set the required values — see Example 1
You will primarily use log.console and ConsoleLogger to control console logging.
This example enables and defines console-based logging settings.
Database.log.console.domains = .all (1)
Database.log.console.level = .verbose (2)| 1 | Define the required domain ; here we turn on logging for all available domains — see: log.console.domains and enum LogDomain |
| 2 | Here we turn on the most verbose log level — see: log.console.level and enum LogLevel. To disable logging for the specified LogDomain set the LogLevel to None.
|
File based logging
File based logging is disabled by default — see: Example 2 for how to enable it.
You will primarily use log.file and FileLogger to control file-based logging.
Formats
Available file based logging formats:
-
Binary — most efficient for storage and performance. It is the default for file based logging.
Use this format and a decoder, such as cbl-log, to view them — see: Decoding binary logs.
-
Plaintext
Configuration
As with console logging you can set the log level — see: the FileLogger class.
With file based logging you can also use the LogFileConfiguration class’s properties to specify the:
-
log file path to the directory to store the log file Once this limit is exceeded a new log file is started.
-
log file format
The default is binary. You can over ride that where necessary and output a plain text log. -
maximum number of rotated log files to keep
-
maximum size of the log file (bytes).
let tempFolder = NSTemporaryDirectory().appending("cbllog")
let config = LogFileConfiguration(directory: tempFolder) (1)
config.usePlainText = true (2)
config.maxSize = 1024 (3)
Database.log.file.config = config (4)
Database.log.file.level = .info (5)| 1 | Set the log file directory |
| 2 | Here we change the max rotation count from the default (1) to 5. Note this means six files may exist at any one time; the five rotated log files, plus the active log file |
| 3 | Here we set the maximum size (bytes) for our log file |
| 4 | Here we select the binary log format (included for reference only as this is the default) |
| 5 | Here we increase the log output level from the default (warnings) to info — see: log.file.level: LogLevel
Note that the use of Database.setLogLevel() is now deprecated. Further, you can no longer set a log level for a specific domain.
|
Custom logging
Couchbase Lite allows for the registration of a callback function to receive Couchbase Lite log messages, which may be logged using any external logging framework.
To do this, apps must implement the Logger interface — see Example 3 — and enable custom logging using log.custom — see Example 4.
Here we introduce the code that implements the Logger interface.
class LogTestLogger: Logger {
// set the log level
var level: LogLevel = .none
// constructor for easiness
init(_ level: LogLevel) {
self.level = level
}
func log(level: LogLevel, domain: LogDomain, message: String) {
// handle the message, for example piping it to
// a third party framework
}
}This example show how to enable the custom logger from <
let logger = LogTestLogger(.warning)
Database.log.custom = logger (1)| 1 | Here we set the custom logger with a level of 'warning'.
The custom logger is called with every log and may choose to filter it, using its configured level.
|
Decoding binary logs
The latest version of the cbl-log tool is 3.0.0.
|
You can use the cbl-log tool to decode binary log files — see Example 5.
-
macOS
-
CentOS
-
Windows
Download the cbl-log tool using wget.
wget https://packages.couchbase.com/releases/couchbase-lite-log/3.0.0/couchbase-lite-log-3.0.0-macos.zipNavigate to the bin directory and run the cbl-log executable.
$ ./cbl-log logcat LOGFILE <OUTPUT_PATH>Download the cbl-log tool using wget.
wget https://packages.couchbase.com/releases/couchbase-lite-log/3.0.0/couchbase-lite-log-3.0.0-centos.zipNavigate to the bin directory and run the cbl-log executable.
cbl-log logcat LOGFILE <OUTPUT_PATH>Download the cbl-log tool using PowerShell.
Invoke-WebRequest https://packages.couchbase.com/releases/couchbase-lite-log/3.0.0/couchbase-lite-log-3.0.0-windows.zip -OutFile couchbase-lite-log-3.0.0-windows.zipRun the cbl-log executable.
$ .\cbl-log.exe logcat LOGFILE <OUTPUT_PATH>