본문 바로가기

Coding/기타

Log Level 구분

- Trace - Only when I would be "tracing" the code and trying to find one part of a function specifically.

 

- Debug - Information that is diagnostically helpful to people more than just developers (IT, sysadmins, etc.)

 

- Info - Generally useful information to log (service start/stop, configuration assumptions, etc). Info I want to always have available but usually don't care about under normal circumstances. This is my out-of-the-box config level.

        - 상태변경과 같은 정보성 메세지 나타낸다

 

- Warn - Anything that can potentially cause application oddities, but for which I am automatically recovering. (Such as switching from a primary to backup server, retrying an operation, missing secondary data, etc.)

        - 처리 가능한 문제, 향후 시스템 에러의 원인이 될 수 있는 경고성 메세지

 

- Error - Any error which is fatal to the operation, but not the service or application (can't open a required file, missing data, etc.). These errors will force user (administrator, or direct user) intervention. These are usually reserved (in my apps) for incorrect connection strings, missing services, etc.

        - 요청을 처리하는 중 문제가 발생한 경우. 

 

- Fatal - Any error that is forcing a shutdown of the service or application to prevent data loss (or further data loss). I reserve these only for the most heinous errors and situations where there is guaranteed to have been data corruption or loss.

        - 아주 심각한 에러가 발생한 상태, 시스템적으로 심각한 문제가 발생해 어플리케이션 작동이 불가능한 경우

 

 

-출처:When to use the different log levels, log4j 로그레벨


'Coding > 기타' 카테고리의 다른 글

덕 타이핑(Duck Typing)  (0) 2020.06.26
TDD(Test-driven Development)  (0) 2020.06.19
VSCode Extension - Draw.io  (0) 2020.05.11
캡슐화(encapsulation)  (0) 2020.05.04
HTTPS와 SSL 인증서  (0) 2020.03.20