couchbaselabs / couchbaselabs/couchbase-shell
Improve logging when http requests return non-200 status
Open
- Dominant language
- Rust
- Stars
- 87
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Probably the status at debug and the body at trace or something like that.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the HTTP request logging entry point in the Rust code and inspect how non-200 responses are currently handled. Confirm the intended log levels and response details with the project before changing them, then verify that non-200 status and response body information appear at the agreed levels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, observability
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100