Lines Matching refs:loggers

331 of components: loggers, handlers, filters, and formatters.
334 * Handlers send the log records (created by loggers) to the appropriate
340 Log event information is passed between loggers, handlers, filters and
344 class (hereafter called :dfn:`loggers`). Each instance has a name, and they are
346 separators. For example, a logger named 'scan' is the parent of loggers
350 A good convention to use when naming loggers is to use a module-level logger,
358 The root of the hierarchy of loggers is called the root logger. That's the
390 The flow of log event information in loggers and handlers is illustrated in the
450 down in the hierarchical list are children of loggers higher up in the list.
451 For example, given a logger with a name of ``foo``, loggers with names of
462 Child loggers propagate messages up to the handlers associated with their
463 ancestor loggers. Because of this, it is unnecessary to define and configure
464 handlers for all the loggers an application uses. It is sufficient to
465 configure handlers for a top-level logger and create child loggers as needed.
555 1. Creating loggers, handlers, and formatters explicitly using Python
624     [loggers]
671    will cause any loggers existing before the :func:`fileConfig` call to
718     loggers:
752 document how the library uses logging - for example, the names of loggers
772 library *foo* is done using loggers with names matching 'foo.x', 'foo.x.y',
783    than* :class:`~logging.NullHandler` *to your library's loggers*. This is
817 Levels can also be associated with loggers, being set either by the developer or
842 Just as for loggers, handlers can have levels associated with them. A handler's
939 Before deciding to process a message further, both loggers and handlers consult
1008    expensive than you'd like (e.g. for deeply nested loggers where an explicit