[FEATURE] Logging: improve logging in the blobber endpoints
- Dominant language
- Go
- Stars
- 20
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
### Problem:
There is zero to none logging in comparison to the errors being catched, without logging it will be almost impossible in later period of time to do RCA for any issue.
### Solution:
Follow logging levels, create configurations, add different loggers with their respective logging level wherever deemed to be with error catching to ensure top observability.
Contributor guide
No contributing guide indexed for this repository
Research direction
Examine the blobber endpoint code to understand the current error handling and identify where logging is missing. Look for existing logging configurations or libraries in the codebase. Determine appropriate logging levels (info, debug, error) and integrate loggers with error catching. Check for any test files to verify logging output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100