Log4net levels

Hi Experts,

i am using log4net.

below are different levels

FATAL
ERROR
WARN
INFO
DEBUG

Error level we are using in exception block but i dont know when and where can i use other levels.

Can u please give small details info about other levels.

Thank you

Hi Prakash,

Let me know you understand or not.

I generally subscribe to the following convention:

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.

Thanks

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Madan Shekar7y ago
Accepted answer
Debug is minimum level, stage level

WARN for production level.

ERROR in case of any exception loging (in catch blog).

INFO this we can use for when we are plaing to write a log line by line.

FATAL in case of any show stoper errors .
+1
Rajanikant Hawaldar7y ago
Hi Prakash,

Let me know you understand or not.

I generally subscribe to the following convention:
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.

Thanks
+1