Eventing : Need a way to specify LCB log level

Description

Currently eventing consumer, which uses libcouchbase, does not provide any way to bump up the SDK log level. As a result, there are times when the end user might just end up seeing the error codes thrown from the SDK to the consumer, which is not always helpful.

Would be great if by default consumer pushes all SDK info level logging to a separate file - maybe something like eventing-lcb.log, and provides the end user with an API to dump up LCB log level. I agree that this might require a consumer restart, but this would greatly help in debugging issues like network between eventing consumer and Query Engine / memcached etc.

Components

Affects versions

Fix versions

Labels

Environment

None

Release Notes Description

None

Activity

Ankit Prabhu February 2, 2021 at 10:24 AM

This will be more useful when user can set the logging dynamically instead of pause, change and resume. Currently lcb will have same log level as eventing individual functions log level.

Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created August 25, 2020 at 4:26 PM
Updated February 4, 2022 at 7:05 AM
Instabug