353 of components: loggers, handlers, filters, and formatters.
355 * Loggers expose the interface that application code directly uses.
356 * Handlers send the log records (created by loggers) to the appropriate
362 Log event information is passed between loggers, handlers, filters and
366 class (hereafter called :dfn:`loggers`). Each instance has a name, and they are
368 separators. For example, a logger named 'scan' is the parent of loggers
372 A good convention to use when naming loggers is to use a module-level logger,
380 The root of the hierarchy of loggers is called the root logger. That's the
414 The flow of log event information in loggers and handlers is illustrated in the
420 Loggers  section in Advanced Logging Tutorial
474 will return a reference to the same logger object.  Loggers that are further
475 down in the hierarchical list are children of loggers higher up in the list.
476 For example, given a logger with a name of ``foo``, loggers with names of
479 Loggers have a concept of *effective level*. If a level is not explicitly set
487 Child loggers propagate messages up to the handlers associated with their
488 ancestor loggers. Because of this, it is unnecessary to define and configure
489 handlers for all the loggers an application uses. It is sufficient to
490 configure handlers for a top-level logger and create child loggers as needed.
591 1. Creating loggers, handlers, and formatters explicitly using Python
662     [loggers]
708    will cause any non-root loggers existing before the :func:`fileConfig`
758     loggers:
805 document how the library uses logging - for example, the names of loggers
826 library *foo* is done using loggers with names matching 'foo.x', 'foo.x.y',
844    than* :class:`~logging.NullHandler` *to your library's loggers*. This is
878 Levels can also be associated with loggers, being set either by the developer or
903 Just as for loggers, handlers can have levels associated with them. A handler's
1006 Before deciding to process a message further, both loggers and handlers consult
1076    expensive than you'd like (e.g. for deeply nested loggers where an explicit