Lines Matching refs:loggers

352 of components: loggers, handlers, filters, and formatters.
355 * Handlers send the log records (created by loggers) to the appropriate
361 Log event information is passed between loggers, handlers, filters and
365 class (hereafter called :dfn:`loggers`). Each instance has a name, and they are
367 separators. For example, a logger named 'scan' is the parent of loggers
371 A good convention to use when naming loggers is to use a module-level logger,
379 The root of the hierarchy of loggers is called the root logger. That's the
413 The flow of log event information in loggers and handlers is illustrated in the
473 down in the hierarchical list are children of loggers higher up in the list.
474 For example, given a logger with a name of ``foo``, loggers with names of
485 Child loggers propagate messages up to the handlers associated with their
486 ancestor loggers. Because of this, it is unnecessary to define and configure
487 handlers for all the loggers an application uses. It is sufficient to
488 configure handlers for a top-level logger and create child loggers as needed.
589 1. Creating loggers, handlers, and formatters explicitly using Python
660     [loggers]
707    will cause any non-root loggers existing before the :func:`fileConfig`
757     loggers:
804 document how the library uses logging - for example, the names of loggers
825 library *foo* is done using loggers with names matching 'foo.x', 'foo.x.y',
836    than* :class:`~logging.NullHandler` *to your library's loggers*. This is
870 Levels can also be associated with loggers, being set either by the developer or
895 Just as for loggers, handlers can have levels associated with them. A handler's
998 Before deciding to process a message further, both loggers and handlers consult
1068    expensive than you'd like (e.g. for deeply nested loggers where an explicit