Seonglae ChoLogging Notion
Logging Analyzers
Logging, the sensible defaults
Logging is a major pillar for well-designed applications. It is not only a large help during development but also critical for failure analysis and debugging. The most effective debugging tool is still careful thought, coupled with judiciously placed print statements. - Brian W. Kernighan Further logging is essential for observability in production. Nonetheless, I often encounter codebases with lousy logging practices. This manifests itself in useless logging missing context or in over-logging thereby bringing down the whole system.
https://gerlacdt.github.io/blog/posts/logging/
Logging practices I follow
No matter what kind of software you're developing, you most definitely leverage logging to some extent, probably every single day.You write a lot of logs, you read tons of them too, it is the most basic observability tool we have. There are many pitfall that can lead to useless, wasteful and confusing logs.
https://www.16elt.com/2023/01/06/logging-practices-I-follow/
로깅과 사용 추적
이 글은 HTTP 완벽가이드 21장을 참고해 정리한 포스팅입니다. 모든 서버와 프락시는 처리한 HTTP 트랜잭션을 요약해서 기록해 놓습니다. 그 이유는 사용추적, 보안, 청구, 에러탐지 등 여러가지 입니다. 로깅을 하는 대개 두가지 이유입니다. HTTP 트랜잭션의 모든 헤더를 로깅할 수는 있지만, 모든 데이터를 그대로 로깅하면 별 연관이 없고 볼일 없는 데이터만 로깅할수도 있습니다.
https://ideveloper2.dev/blog/2020-02-23--%EB%A1%9C%EA%B9%85%EA%B3%BC-%EC%82%AC%EC%9A%A9-%EC%B6%94%EC%A0%81/
