I have been waiting for so long to understand how logging works using logging configuration file, So in this post I will just be focussing on logging configuration file how we can log message to shell as well as disk using logging.StreamHandler Class and logging.FileHandler Class.
The user of the logging package makes logging calls on instances of Logger, which are organized into a hierarchy based on a "dotted name" namespace. This hierarchy is embodied in an encapsulated singleton Manager instance (which can be ignored by users of the package, for most purposes). Based on the type of logging call and the logging configuration (see below)
So First just logging to terminal.
The user of the logging package makes logging calls on instances of Logger, which are organized into a hierarchy based on a "dotted name" namespace. This hierarchy is embodied in an encapsulated singleton Manager instance (which can be ignored by users of the package, for most purposes). Based on the type of logging call and the logging configuration (see below)
So First just logging to terminal.
the call may be passed through a set of Filter instances to decide whether it should be dropped. If not, then the logger consults a set of Handler instances which are associated with it, and asks each handler instance to "handle" the logging event. By default, the system moves up the namespace hierarchy and invokes handlers on all loggers at or above the level of the logger on which the logging call was made. (You can override this by setting a logger's "propagate" attribute to 0 - no traversal up the hierarchy is made from such a logger.
Now I will move on to logging to shell as well as file simultaneously. In the below example of logging configuration file I will comment the description of loggers, Formatters, Handlers etc.
Now I will move on to logging to shell as well as file simultaneously. In the below example of logging configuration file I will comment the description of loggers, Formatters, Handlers etc.
RSS Feed
