Lines Matching full:handlers
33 in :mod:`logging` itself) and defining handlers which are declared either in
34 :mod:`logging` or :mod:`logging.handlers`.
282 * *handlers* - the corresponding value will be a dict in which each
307 handlers:
315 class : logging.handlers.RotatingFileHandler
324 :class:`logging.handlers.RotatingFileHandler` with the keyword arguments
343 * ``handlers`` (optional). A list of ids of the handlers for this
347 propagation, filters and handlers specified.
379 the object graph of loggers, handlers, filters, formatters at
381 handlers can be controlled just by setting levels (and, in the case of
390 settings in the ``handlers`` entries, and the ``level`` and
404 handlers, formatters, filters - which are connected to each other in
426 handlers:
436 handlers: [h1, h2]
450 have two handlers attached to it, which are described by the handler
461 The schema supports user-defined objects for handlers, filters and
547 The ``filters`` member of ``handlers`` and ``loggers`` can take
580 Handlers are configured in alphabetical order of their keys, and a configured
582 ``handlers`` dictionary in the schema. If you use a construct such as
583 ``cfg://handlers.foo``, then initially ``handlers['foo']`` points to the
586 Thus, ``cfg://handlers.foo`` could resolve to either a dictionary or a handler
587 instance. In general, it is wise to name handlers in a way such that dependent
588 handlers are configured _after_ any handlers they depend on; that allows
589 something like ``cfg://handlers.foo`` to be used in configuring a handler that
594 after ``foo``, with the result that ``cfg://handlers.foo`` would resolve to
635 ``handlers``, ``filters`` and ``formatter`` entries will take an
640 example, consider :class:`logging.handlers.MemoryHandler`, which takes
652 handlers:
658 alternate: cfg://handlers.file
660 The literal string ``'cfg://handlers.file'`` will be resolved in an
668 handlers:
670 class: logging.handlers.SMTPHandler
678 in the configuration, the string ``'cfg://handlers'`` would resolve to
679 the dict with key ``handlers``, the string ``'cfg://handlers.email``
680 would resolve to the dict with key ``email`` in the ``handlers`` dict,
681 and so on. The string ``'cfg://handlers.email.toaddrs[1]`` would
683 ``'cfg://handlers.email.toaddrs[0]'`` would resolve to the value
685 using either ``'cfg://handlers.email.subject'`` or, equivalently,
686 ``'cfg://handlers.email[subject]'``. The latter form only needs to be
692 Given a string ``cfg://handlers.myhandler.mykey.123``, this will
693 resolve to ``config_dict['handlers']['myhandler']['mykey']['123']``.
694 If the string is specified as ``cfg://handlers.myhandler.mykey[123]``,
696 ``config_dict['handlers']['myhandler']['mykey'][123]``, and fall back
697 to ``config_dict['handlers']['myhandler']['mykey']['123']`` if that
732 ``[loggers]``, ``[handlers]`` and ``[formatters]`` which identify by name the
737 handler called ``hand01`` in the ``[handlers]`` section will have its
762 [handlers]
768 The root logger must specify a level and a list of handlers. An example of a
775 handlers=hand01
782 The ``handlers`` entry is a comma-separated list of handler names, which must
783 appear in the ``[handlers]`` section. These names must appear in the
784 ``[handlers]`` section and have corresponding sections in the configuration
794 handlers=hand01
798 The ``level`` and ``handlers`` entries are interpreted as for the root logger,
802 propagate to handlers higher up the logger hierarchy from this logger, or 0 to
803 indicate that messages are **not** propagated to handlers up the hierarchy. The
828 class. Refer to the constructors for the relevant handlers, or to the examples
845 class=handlers.SocketHandler
848 args=('localhost', handlers.DEFAULT_TCP_LOGGING_PORT)
851 class=handlers.DatagramHandler
854 args=('localhost', handlers.DEFAULT_UDP_LOGGING_PORT)
857 class=handlers.SysLogHandler
860 args=(('localhost', handlers.SYSLOG_UDP_PORT), handlers.SysLogHandler.LOG_USER)
863 class=handlers.NTEventLogHandler
869 class=handlers.SMTPHandler
876 class=handlers.MemoryHandler
883 class=handlers.HTTPHandler
917 Module :mod:`logging.handlers`
918 Useful handlers included with the logging module.