• how-to
    Logging with gocb.Logger & using other implementations.

    The Go SDK offers simple logging of library internals to help debug issues. Logging may be configured on a global library-level basis. Note that the logging API is subject to change.

    You can configure logging using the gocb.SetLogger, which accepts an implementation of gocb.Logger. The SDK comes with two built-in Logger implementations, which can be instantiated using the following methods:

    • gocb.DefaultStdioLogger() returns a logger that logs errors and warnings. This is fairly non-disruptive and does not produce a lot of output.

    • gocb.VerboseStdioLogger() returns a logger that logs more detailed tracing information. This logger should only be used when trying to diagnose an issue.

    import (
    func main() {
            // Use the gocb library.

    It is also possible to provide other logger implementations to gocb.SetLogger. Implementations must satisify the gocb.Logger interface.

      type Logger interface {
    	// Outputs logging information:
    	// level is the verbosity level
    	// offset is the position within the calling stack from which the message
    	// originated. This is useful for contextual loggers which retrieve file/line
    	// information.
    	Log(level LogLevel, offset int, format string, v ...interface{}) error

    The gocb.DefaultStdioLogger() and gocb.VerboseStdioLogger() wrap their gocbcore counterparts to provide a stable interface. The gocb versions should be used.

    Log Redaction

    Redacting logs is a two-stage process. If you want to redact client logs (for example before handing them off to the Couchbase Support team) you first need to enable log redaction in your application.


    Different redaction levels are supported — please see the RedactionLevel enum description for more information.

    Note that you need to run this command before any of the SDK code is initialized so all of the logs are captured properly. Once the SDK writes the logs with the tags to a file, you can then use the cblogredaction tool to obfuscate the log.

    Using your own Logger

    Sometimes you want to use your own logger with the SDK. You might want your logging to use a popular logging framework such as logrus. In the following examples we show to use the SDK with a logrus logger:

    First we need to create our own logger that wraps the logrus logger. The logrus Log/Logf functions don’t quite match the gocb logging interface and the log levels are slightly different. This means that we need to do a bit of marshalling to get the data into a set of parameters that logrus can use.

    type MyLogrusLogger struct {
    	logger *logrus.Logger
    // The logrus Log function doesn't match the gocb Log function so we need to do a bit of marshalling.
    func (logger *MyLogrusLogger) Log(level gocb.LogLevel, offset int, format string, v ...interface{}) error {
    	// We need to do some conversion between gocb and logrus levels as they don't match up.
    	var logrusLevel logrus.Level
    	switch level {
    	case gocb.LogError:
    		logrusLevel = logrus.ErrorLevel
    	case gocb.LogWarn:
    		logrusLevel = logrus.WarnLevel
    	case gocb.LogInfo:
    		logrusLevel = logrus.InfoLevel
    	case gocb.LogDebug:
    		logrusLevel = logrus.DebugLevel
    	case gocb.LogTrace:
    		logrusLevel = logrus.TraceLevel
    	case gocb.LogSched:
    		logrusLevel = logrus.TraceLevel
    	case gocb.LogMaxVerbosity:
    		logrusLevel = logrus.TraceLevel
    	// Send the data to the logrus Logf function to make sure that it gets formatted correctly.
    	logger.logger.Logf(logrusLevel, format, v...)
    	return nil

    Next we need to create a logrus logger instance, wrap it in our own logger and then pass it to gocb:

    	logger := logrus.New()
    		logger: logger,

    Now all of the gocb logging output will go through our logger and be outputted to stdout (e.g. the terminal) in JSON.