353 of components: loggers, handlers, filters, and formatters.
356 * Handlers send the log records (created by loggers) to the appropriate
362 Log event information is passed between loggers, handlers, filters and
414 The flow of log event information in loggers and handlers is illustrated in the
427 objects pass along relevant log messages to all interested log handlers.
441   handler objects from the logger object.  Handlers are covered in more detail
485 determine whether the event is passed to the logger's handlers.
487 Child loggers propagate messages up to the handlers associated with their
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.
497 Handlers  section in Advanced Logging Tutorial
506 email address. This scenario requires three individual handlers where each
511 :ref:`useful-handlers`); the tutorials use mainly :class:`StreamHandler` and
517 custom handlers) are the following configuration methods:
522   determines which severity of messages it will pass to its handlers.  The level
529   configure and deconfigure filter objects on handlers.
533 defines the interface that all handlers should have and establishes some
591 1. Creating loggers, handlers, and formatters explicitly using Python
665     [handlers]
673     handlers=consoleHandler
677     handlers=consoleHandler
726 :class:`~logging.handlers.WatchedFileHandler` (relative to the logging module) or
752     handlers:
761         handlers: [console]
765       handlers: [console]
774 where a logging event needs to be output, but no handlers can be found to
784   'No handlers could be found for logger X.Y.Z' is printed once.
817 that configuration will add some handlers, and if levels are suitably
819 handlers, as normal.
840    the application developer to configure the logging verbosity or handlers of
843 .. note:: It is strongly advised that you *do not add any handlers other
845    because the configuration of handlers is the prerogative of the application
847    target audience and what handlers are most appropriate for their
848    application: if you add handlers 'under the hood', you might well interfere
890 :dfn:`handlers`, which are instances of subclasses of the :class:`Handler`
891 class. Handlers are responsible for ensuring that a logged message (in the form
894 support desk staff, system administrators, developers). Handlers are passed
896 can have zero, one or more handlers associated with it (via the
898 handlers directly associated with a logger, *all handlers associated with all
901 passing to ancestor handlers stops).
903 Just as for loggers, handlers can have levels associated with them. A handler's
924 .. _useful-handlers:
926 Useful Handlers
937 #. :class:`~handlers.BaseRotatingHandler` is the base class for handlers that
939    directly. Instead, use :class:`~handlers.RotatingFileHandler` or
940    :class:`~handlers.TimedRotatingFileHandler`.
942 #. :class:`~handlers.RotatingFileHandler` instances send messages to disk
945 #. :class:`~handlers.TimedRotatingFileHandler` instances send messages to
948 #. :class:`~handlers.SocketHandler` instances send messages to TCP/IP
951 #. :class:`~handlers.DatagramHandler` instances send messages to UDP
954 #. :class:`~handlers.SMTPHandler` instances send messages to a designated
957 #. :class:`~handlers.SysLogHandler` instances send messages to a Unix
960 #. :class:`~handlers.NTEventLogHandler` instances send messages to a
963 #. :class:`~handlers.MemoryHandler` instances send messages to a buffer
966 #. :class:`~handlers.HTTPHandler` instances send messages to an HTTP
969 #. :class:`~handlers.WatchedFileHandler` instances watch the file they are
974 #. :class:`~handlers.QueueHandler` instances send messages to a queue, such as
979    handlers could be found for logger XXX' message which can be displayed if
987    The :class:`~handlers.QueueHandler` class.
990 classes are defined in the core logging package. The other handlers are
991 defined in a sub-module, :mod:`logging.handlers`. (There is also another
999 :class:`~handlers.BufferingFormatter` can be used. In addition to the format
1006 Before deciding to process a message further, both loggers and handlers consult
1053 :class:`~handlers.SocketHandler` emits an event by pickling it and sending it
1106 Also note that the core logging module only includes the basic handlers. If
1107 you don't import :mod:`logging.handlers` and :mod:`logging.config`, they won't
1118    Module :mod:`logging.handlers`
1119       Useful handlers included with the logging module.