Lines Matching refs:loggers

343 of components: loggers, handlers, filters, and formatters.
346 * Handlers send the log records (created by loggers) to the appropriate
352 Log event information is passed between loggers, handlers, filters and
356 class (hereafter called :dfn:`loggers`). Each instance has a name, and they are
358 separators. For example, a logger named 'scan' is the parent of loggers
362 A good convention to use when naming loggers is to use a module-level logger,
370 The root of the hierarchy of loggers is called the root logger. That's the
404 The flow of log event information in loggers and handlers is illustrated in the
464 down in the hierarchical list are children of loggers higher up in the list.
465 For example, given a logger with a name of ``foo``, loggers with names of
476 Child loggers propagate messages up to the handlers associated with their
477 ancestor loggers. Because of this, it is unnecessary to define and configure
478 handlers for all the loggers an application uses. It is sufficient to
479 configure handlers for a top-level logger and create child loggers as needed.
580 1. Creating loggers, handlers, and formatters explicitly using Python
651     [loggers]
698    will cause any non-root loggers existing before the :func:`fileConfig`
748     loggers:
795 document how the library uses logging - for example, the names of loggers
816 library *foo* is done using loggers with names matching 'foo.x', 'foo.x.y',
827    than* :class:`~logging.NullHandler` *to your library's loggers*. This is
861 Levels can also be associated with loggers, being set either by the developer or
886 Just as for loggers, handlers can have levels associated with them. A handler's
989 Before deciding to process a message further, both loggers and handlers consult
1059    expensive than you'd like (e.g. for deeply nested loggers where an explicit