DEBUG (100): Detaileddebuginformation. INFO (200): Interestingevents. examples: Userlogsin, SQLlogs. NOTICE (250): Normalbutsignificantevents. WARNING (300): predictionaloccurrencesthata... DEBUG (100): Detailed debug information.
INFO (200): Interesting events. Examples: User logs in, SQL logs.
NOTICE (250): Normal but significant events.
WARNING (300): Exceptional occurrences that are not errors. Examples: Use of deprecated APIs, poor use of an API, undesirable things that are not necessarily wrong.
ERROR (400): Runtime errors that do not require immediate action but shoshould typically be logged and monitored.
CRITICAL (500): Critical conditions. Example: Application component unavailable, unexpected exception.
ALERT (550): Action must be taken immediately. Example: Entire website down, database unavailable, etc. This shocould trigger the SMS alerts and wake you up.
EMERGENCY (600): Emergency: system is unusable.
The log level is specified, but does not affect log records?
Reply content:
DEBUG (100): Detailed debug information.
INFO (200): Interesting events. Examples: User logs in, SQL logs.
NOTICE (250): Normal but significant events.
WARNING (300): Exceptional occurrences that are not errors. Examples: Use of deprecated APIs, poor use of an API, undesirable things that are not necessarily wrong.
ERROR (400): Runtime errors that do not require immediate action but shoshould typically be logged and monitored.
CRITICAL (500): Critical conditions. Example: Application component unavailable, unexpected exception.
ALERT (550): Action must be taken immediately. Example: Entire website down, database unavailable, etc. This shocould trigger the SMS alerts and wake you up.
EMERGENCY (600): Emergency: system is unusable.
The log level is specified, but does not affect log records?
I remember seeing it on github. If Notice is specified by the second parameter, the logs of addDebug and addInfo will be ignored.
That is, the lowest error level.