This is part of the Observability/Threshold Logging that is included in the SDK - it’s there so you are able to track slow operations that are taking longer than the set threshold, and therefore debug issues.
If you want to reduce the number of these messages then in your CouchbaseEnvironment, you could try increasing the queryThreshold time so that these slow operations do not exceed the threshold, and/or increase the emitInterval duration to reduce how often these messages are displayed. For example:
It’s also worth mentioning that the thresholds were selected to be somewhat conservative. It’s impossible for the Couchbase SDK to know what is reasonably closer to your service level objective and what is not though. Some users, for example, run on 10gigE networks with large systems and have very low latencies, other users run on small instances on cloud providers and intentionally have all data on slower disks. Those have very different performance profiles.
What we hope is that if you see these requests over the threshold, it prompts you to think about it a bit and adjust the thresholds to something that makes sense for your service level objective. Then it helps you manage to that.