No option to change logging level for a specific Cluster instance

This is being raised based on experience from goldfish-nebula project:

 go 1.20

 require (

     github.com/caarlos0/env/v6 v6.10.1

     github.com/couchbase/go_json v0.0.0-20230326140031-d6e17ad2b9a2

     github.com/couchbase/gocb/v2 v2.6.3

     github.com/couchbase/gocbcore/v9 v9.1.10

     github.com/google/uuid v1.3.0

     github.com/gorilla/mux v1.8.0

     go.uber.org/zap v1.24.0

 )

 require (

     github.com/couchbase/gocbcore/v10 v10.2.3 // indirect

     github.com/golang/snappy v0.0.4 // indirect

     go.uber.org/atomic v1.7.0 // indirect

     go.uber.org/multierr v1.6.0 // indirect

 )

The process hosts multiple gocb.Cluster instances. For debugging purposes, we need to enable verbose logging on one of many cluster instances.

However, it seems logging can be changed at the library level, not at individual cluster instance, which is not expected and hence looks like a bug.

If you still decide on keeping logging at the library level, log statements from cluster instances should be tagged with a cookie (probably cluster instance Id).

This will help the user in implementing a custom logger that can segregate log messages from different cluster instances.