Background/Goal
Key task for OKR O 6. KR3
As a software engineer in wme i'd like to have a document specifying the logging standards for the team, so that i can rely on it for my work and guarantee quality of logs.
We have a logging package with a defined API for formatted json logs, in this document i'd expect to have a criteria of what to include and what levels to use in what cases.
Acceptance Criteria
- Document specifying the teams best practices going forward.
- Template proposal for the team to discuss
Key Tasks
- Document specifying the following for logs:
- What logs levels available
- Per log level, how and what should the logs be created.
- Document specifying the following for metrics:
- Present to the team and iterate given feedback.
Artifacts & Resources
- https://gogoapps.io/blog/passing-loggers-in-go-golang-logging-best-practices/
- https://devcenter.heroku.com/articles/writing-best-practices-for-application-logs
- https://medium.com/codex/level-based-logging-in-go-with-uber-zap-a8a90aa40672
- https://levelup.gitconnected.com/9-logging-best-practices-da9457e33305