-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Logging: improve logging in the blobber endpoints #290
Labels
Projects
Milestone
Comments
linked to 0chain/0chain#417 |
@cnlangzi I like to work on it. |
completely agreed @kushthedude - I'd like to see each request logged with a unique transaction id and return this to the user on error https://0chain.slack.com/archives/C028ZCJT6LU/p1628543067137800 |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: