Lines Matching full:handlers

34 in :mod:`logging` itself) and defining handlers which are declared either in
35 :mod:`logging` or :mod:`logging.handlers`.
194 * *handlers* - the corresponding value will be a dict in which each
216       handlers:
224           class : logging.handlers.RotatingFileHandler
233   :class:`logging.handlers.RotatingFileHandler` with the keyword arguments
249   * ``handlers`` (optional).  A list of ids of the handlers for this
253   propagation, filters and handlers specified.
285 the object graph of loggers, handlers, filters, formatters at
287 handlers can be controlled just by setting levels (and, in the case of
296 settings in the ``handlers`` entries, and the ``level`` and
310 handlers, formatters, filters - which are connected to each other in
332     handlers:
342         handlers: [h1, h2]
356 have two handlers attached to it, which are described by the handler
367 The schema supports user-defined objects for handlers, filters and
485 ``handlers``, ``filters`` and ``formatter`` entries will take an
490 example, consider :class:`logging.handlers.MemoryHandler`, which takes
500     handlers:
506         alternate: cfg://handlers.file
508 The literal string ``'cfg://handlers.file'`` will be resolved in an
514     handlers:
516         class: logging.handlers.SMTPHandler
524 in the configuration, the string ``'cfg://handlers'`` would resolve to
525 the dict with key ``handlers``, the string ``'cfg://handlers.email``
526 would resolve to the dict with key ``email`` in the ``handlers`` dict,
527 and so on.  The string ``'cfg://handlers.email.toaddrs[1]`` would
529 ``'cfg://handlers.email.toaddrs[0]'`` would resolve to the value
531 using either ``'cfg://handlers.email.subject'`` or, equivalently,
532 ``'cfg://handlers.email[subject]'``.  The latter form only needs to be
538 Given a string ``cfg://handlers.myhandler.mykey.123``, this will
539 resolve to ``config_dict['handlers']['myhandler']['mykey']['123']``.
540 If the string is specified as ``cfg://handlers.myhandler.mykey[123]``,
542 ``config_dict['handlers']['myhandler']['mykey'][123]``, and fall back
543 to ``config_dict['handlers']['myhandler']['mykey']['123']`` if that
578 ``[loggers]``, ``[handlers]`` and ``[formatters]`` which identify by name the
583 handler called ``hand01`` in the ``[handlers]`` section will have its
608    [handlers]
614 The root logger must specify a level and a list of handlers. An example of a
621    handlers=hand01
628 The ``handlers`` entry is a comma-separated list of handler names, which must
629 appear in the ``[handlers]`` section. These names must appear in the
630 ``[handlers]`` section and have corresponding sections in the configuration
640    handlers=hand01
644 The ``level`` and ``handlers`` entries are interpreted as for the root logger,
648 propagate to handlers higher up the logger hierarchy from this logger, or 0 to
649 indicate that messages are **not** propagated to handlers up the hierarchy. The
678 class. Refer to the constructors for the relevant handlers, or to the examples
690    class=handlers.SocketHandler
693    args=('localhost', handlers.DEFAULT_TCP_LOGGING_PORT)
696    class=handlers.DatagramHandler
699    args=('localhost', handlers.DEFAULT_UDP_LOGGING_PORT)
702    class=handlers.SysLogHandler
705    args=(('localhost', handlers.SYSLOG_UDP_PORT), handlers.SysLogHandler.LOG_USER)
708    class=handlers.NTEventLogHandler
714    class=handlers.SMTPHandler
720    class=handlers.MemoryHandler
727    class=handlers.HTTPHandler
768    Module :mod:`logging.handlers`
769       Useful handlers included with the logging module.