controlling the amount of information logged controlling the amount of information logged log messages are actually associated with log level these log levels are intended to indicate the severity of the message being logged there are six different log levels associated with the python logging frameworkthese arenotset at this level no logging takes place and logging is effectively turned off debug this level is intended to provide detailed informationtypically of interest when developer is diagnosing bug or issues within an application info this level is expected to provide less detail than the debug log level as it is expected to provide information that can be used to confirm that the application is working as expected warning this is used to provide information on an unexpected event or an indication of some likely problem that developer or system administration might wish to investigate further error this is used to provide information on some serious issue or problem that the application has not been able to deal with and that is likely to mean that the application cannot function correctly critical this is the highest level of issue and is reserved for critical situations such as ones in which the program can no longer continue executing the log levels are relative to one another and defined in hierarchy each log level has numeric value associated with it as shown below (although you should never need to use the numbersthus info is higher log level than debugin turn error is higher log level than warninginfodebug etc associated with the log level that message is logged witha logger also has log level associated with it the logger will process all messages that are at the loggers log level or above that level thus if logger has log level of warning then it will log all messages logged using the warningerror and critical log levels generally speakingan application will not use the debug level in production system this is usually considered inappropriate as it is only intended for debug scenarios the info level may be considered appropriate for production system although it is likely to produce large amounts of information as it typically traces the execution of functions and methods if an application has been well tested and verified then it is only really warnings and errors which should occur/be of concern it is therefore not uncommon to default to the warning level for production