Lines Matching refs:handlers

33 in :mod:`logging` itself) and defining handlers which are declared either in
34 :mod:`logging` or :mod:`logging.handlers`.
274 * *handlers* - the corresponding value will be a dict in which each
296       handlers:
304           class : logging.handlers.RotatingFileHandler
313   :class:`logging.handlers.RotatingFileHandler` with the keyword arguments
329   * ``handlers`` (optional).  A list of ids of the handlers for this
333   propagation, filters and handlers specified.
365 the object graph of loggers, handlers, filters, formatters at
367 handlers can be controlled just by setting levels (and, in the case of
376 settings in the ``handlers`` entries, and the ``level`` and
390 handlers, formatters, filters - which are connected to each other in
412     handlers:
422         handlers: [h1, h2]
436 have two handlers attached to it, which are described by the handler
447 The schema supports user-defined objects for handlers, filters and
565 ``handlers``, ``filters`` and ``formatter`` entries will take an
570 example, consider :class:`logging.handlers.MemoryHandler`, which takes
582     handlers:
588         alternate: cfg://handlers.file
590 The literal string ``'cfg://handlers.file'`` will be resolved in an
598     handlers:
600         class: logging.handlers.SMTPHandler
608 in the configuration, the string ``'cfg://handlers'`` would resolve to
609 the dict with key ``handlers``, the string ``'cfg://handlers.email``
610 would resolve to the dict with key ``email`` in the ``handlers`` dict,
611 and so on.  The string ``'cfg://handlers.email.toaddrs[1]`` would
613 ``'cfg://handlers.email.toaddrs[0]'`` would resolve to the value
615 using either ``'cfg://handlers.email.subject'`` or, equivalently,
616 ``'cfg://handlers.email[subject]'``.  The latter form only needs to be
622 Given a string ``cfg://handlers.myhandler.mykey.123``, this will
623 resolve to ``config_dict['handlers']['myhandler']['mykey']['123']``.
624 If the string is specified as ``cfg://handlers.myhandler.mykey[123]``,
626 ``config_dict['handlers']['myhandler']['mykey'][123]``, and fall back
627 to ``config_dict['handlers']['myhandler']['mykey']['123']`` if that
662 ``[loggers]``, ``[handlers]`` and ``[formatters]`` which identify by name the
667 handler called ``hand01`` in the ``[handlers]`` section will have its
692    [handlers]
698 The root logger must specify a level and a list of handlers. An example of a
705    handlers=hand01
712 The ``handlers`` entry is a comma-separated list of handler names, which must
713 appear in the ``[handlers]`` section. These names must appear in the
714 ``[handlers]`` section and have corresponding sections in the configuration
724    handlers=hand01
728 The ``level`` and ``handlers`` entries are interpreted as for the root logger,
732 propagate to handlers higher up the logger hierarchy from this logger, or 0 to
733 indicate that messages are **not** propagated to handlers up the hierarchy. The
758 class. Refer to the constructors for the relevant handlers, or to the examples
775    class=handlers.SocketHandler
778    args=('localhost', handlers.DEFAULT_TCP_LOGGING_PORT)
781    class=handlers.DatagramHandler
784    args=('localhost', handlers.DEFAULT_UDP_LOGGING_PORT)
787    class=handlers.SysLogHandler
790    args=(('localhost', handlers.SYSLOG_UDP_PORT), handlers.SysLogHandler.LOG_USER)
793    class=handlers.NTEventLogHandler
799    class=handlers.SMTPHandler
806    class=handlers.MemoryHandler
813    class=handlers.HTTPHandler
847    Module :mod:`logging.handlers`
848       Useful handlers included with the logging module.