Mr.Combet Webshell 🔥

Edit File Name : logging.handlers.html

<!DOCTYPE html>

<title>logging.handlers — Logging handlers &#8212; Python 3.12.3 documentation</title><meta name="viewport" content="width=device-width, initial-scale=1.0">
 
 <link rel="stylesheet" type="text/css" href="../_static/pygments.css?v=80d5e7a1" />
 <link rel="stylesheet" type="text/css" href="../_static/pydoctheme.css?v=bb723527" />
 <link id="pygments_dark_css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css" href="../_static/pygments_dark.css?v=b20cc3f5" />
 
 <script src="../_static/documentation_options.js?v=2c828074"></script>
 <script src="../_static/doctools.js?v=888ff710"></script>
 <script src="../_static/sphinx_highlight.js?v=dc90522c"></script>
 
 <script src="../_static/sidebar.js"></script>
 
 <link rel="search" type="application/opensearchdescription+xml"
 title="Search within Python 3.12.3 documentation"
 href="../_static/opensearch.xml"/>
 <link rel="author" title="About these documents" href="../about.html" />
 <link rel="index" title="Index" href="../genindex.html" />
 <link rel="search" title="Search" href="../search.html" />
 <link rel="copyright" title="Copyright" href="../copyright.html" />
 <link rel="next" title="getpass — Portable password input" href="getpass.html" />
 <link rel="prev" title="logging.config — Logging configuration" href="logging.config.html" />
 <link rel="canonical" href="https://docs.python.org/3/library/logging.handlers.html" />

</head>
<body>
<div class="mobile-nav">
 <input type="checkbox" id="menuToggler" class="toggler__input" aria-controls="navigation"
 aria-pressed="false" aria-expanded="false" role="button" aria-label="Menu" />
 <nav class="nav-content" role="navigation">
 <label for="menuToggler" class="toggler__label">
 
 </label>
 
 <a href="https://www.python.org/" class="nav-logo">
 <img src="../_static/py.svg" alt="Python logo"/>
 </a>
 
 <form role="search" class="search" action="../search.html" method="get">
 <svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" class="search-icon">
 <path fill-rule="nonzero" fill="currentColor" d="M15.5 14h-.79l-.28-.27a6.5 6.5 0 001.48-5.34c-.47-2.78-2.79-5-5.59-5.34a6.505 6.505 0 00-7.27 7.27c.34 2.8 2.56 5.12 5.34 5.59a6.5 6.5 0 005.34-1.48l.27.28v.79l4.25 4.25c.41.41 1.08.41 1.49 0 .41-.41.41-1.08 0-1.49L15.5 14zm-6 0C7.01 14 5 11.99 5 9.5S7.01 5 9.5 5 14 7.01 14 9.5 11.99 14 9.5 14z"></path>
 </svg>
 <input placeholder="Quick search" aria-label="Quick search" type="search" name="q" />
 <input type="submit" value="Go"/>
 </form>
 
 </nav>
 <div class="menu-wrapper">
 <nav class="menu" role="navigation" aria-label="main navigation">
 <div class="language_switcher_placeholder"></div>
 
<label class="theme-selector-label">
 Theme
 <select class="theme-selector" oninput="activateTheme(this.value)">
 <option value="auto" selected>Auto</option>
 <option value="light">Light</option>
 <option value="dark">Dark</option>
 </select>
</label>
 <div>
 <h3><a href="../contents.html">Table of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#"><code class="xref py py-mod docutils literal notranslate">logging.handlers</code> — Logging handlers</a><ul>
<li><a class="reference internal" href="#streamhandler">StreamHandler</a></li>
<li><a class="reference internal" href="#filehandler">FileHandler</a></li>
<li><a class="reference internal" href="#nullhandler">NullHandler</a></li>
<li><a class="reference internal" href="#watchedfilehandler">WatchedFileHandler</a></li>
<li><a class="reference internal" href="#baserotatinghandler">BaseRotatingHandler</a></li>
<li><a class="reference internal" href="#rotatingfilehandler">RotatingFileHandler</a></li>
<li><a class="reference internal" href="#timedrotatingfilehandler">TimedRotatingFileHandler</a></li>
<li><a class="reference internal" href="#sockethandler">SocketHandler</a></li>
<li><a class="reference internal" href="#datagramhandler">DatagramHandler</a></li>
<li><a class="reference internal" href="#sysloghandler">SysLogHandler</a></li>
<li><a class="reference internal" href="#nteventloghandler">NTEventLogHandler</a></li>
<li><a class="reference internal" href="#smtphandler">SMTPHandler</a></li>
<li><a class="reference internal" href="#memoryhandler">MemoryHandler</a></li>
<li><a class="reference internal" href="#httphandler">HTTPHandler</a></li>
<li><a class="reference internal" href="#queuehandler">QueueHandler</a></li>
<li><a class="reference internal" href="#queuelistener">QueueListener</a></li>
</ul>
</li>
</ul>

</div>
 <div>
 <h4>Previous topic</h4>
 <a href="logging.config.html"
 title="previous chapter"><code class="xref py py-mod docutils literal notranslate">logging.config</code> — Logging configuration</a>
 </div>
 <div>
 <h4>Next topic</h4>
 <a href="getpass.html"
 title="next chapter"><code class="xref py py-mod docutils literal notranslate">getpass</code> — Portable password input</a>
 </div>
 <div role="note" aria-label="source link">
 <h3>This Page</h3>
 <ul class="this-page-menu">
 <li><a href="../bugs.html">Report a Bug</a></li>
 <li>
 <a href="https://github.com/python/cpython/blob/main/Doc/library/logging.handlers.rst"
 rel="nofollow">Show Source
 </a>
 </li>
 </ul>
 </div>
 </nav>
 </div>
</div>

<div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 accesskey="I">index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="getpass.html" title="getpass — Portable password input"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="logging.config.html" title="logging.config — Logging configuration"
 accesskey="P">previous</a> |</li>

<li><img src="../_static/py.svg" alt="Python logo" style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="https://www.python.org/">Python</a> &#187;</li>
 <li class="switchers">
 <div class="language_switcher_placeholder"></div>
 <div class="version_switcher_placeholder"></div>
 </li>
 <li>
 
 </li>
 <li id="cpython-language-and-version">
 <a href="../index.html">3.12.3 Documentation</a> &#187;
 </li>

<li class="nav-item nav-item-1"><a href="index.html" >The Python Standard Library</a> &#187;</li>
 <li class="nav-item nav-item-2"><a href="allos.html" accesskey="U">Generic Operating System Services</a> &#187;</li>
 <li class="nav-item nav-item-this"><a href=""><code class="xref py py-mod docutils literal notranslate">logging.handlers</code> — Logging handlers</a></li>
 <li class="right">

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body" role="main">
 
 <section id="module-logging.handlers">
<h1><a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a> — Logging handlers<a class="headerlink" href="#module-logging.handlers" title="Link to this heading">¶</a></h1>
Source code: <a class="reference external" href="https://github.com/python/cpython/tree/3.12/Lib/logging/handlers.py">Lib/logging/handlers.py</a>
<aside class="sidebar">
Important
This page contains only reference information. For tutorials,
please see
<ul class="simple">
<li><a class="reference internal" href="../howto/logging.html#logging-basic-tutorial">Basic Tutorial</a></li>
<li><a class="reference internal" href="../howto/logging.html#logging-advanced-tutorial">Advanced Tutorial</a></li>
<li><a class="reference internal" href="../howto/logging-cookbook.html#logging-cookbook">Logging Cookbook</a></li>
</ul>
</aside>
<hr class="docutils" />
The following useful handlers are provided in the package. Note that three of
the handlers (<a class="reference internal" href="#logging.StreamHandler" title="logging.StreamHandler"><code class="xref py py-class docutils literal notranslate">StreamHandler</code></a>, <a class="reference internal" href="#logging.FileHandler" title="logging.FileHandler"><code class="xref py py-class docutils literal notranslate">FileHandler</code></a> and
<a class="reference internal" href="#logging.NullHandler" title="logging.NullHandler"><code class="xref py py-class docutils literal notranslate">NullHandler</code></a>) are actually defined in the <a class="reference internal" href="logging.html#module-logging" title="logging: Flexible event logging system for applications."><code class="xref py py-mod docutils literal notranslate">logging</code></a> module itself,
but have been documented here along with the other handlers.
<section id="streamhandler">
<h2>StreamHandler<a class="headerlink" href="#streamhandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.StreamHandler" title="logging.StreamHandler"><code class="xref py py-class docutils literal notranslate">StreamHandler</code></a> class, located in the core <a class="reference internal" href="logging.html#module-logging" title="logging: Flexible event logging system for applications."><code class="xref py py-mod docutils literal notranslate">logging</code></a> package,
sends logging output to streams such as sys.stdout, sys.stderr or any
file-like object (or, more precisely, any object which supports <code class="xref py py-meth docutils literal notranslate">write()</code>
and <code class="xref py py-meth docutils literal notranslate">flush()</code> methods).
<dl class="py class">
<dt class="sig sig-object py" id="logging.StreamHandler">
class logging.StreamHandler(stream=None)<a class="headerlink" href="#logging.StreamHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.StreamHandler" title="logging.StreamHandler"><code class="xref py py-class docutils literal notranslate">StreamHandler</code></a> class. If stream is
specified, the instance will use it for logging output; otherwise, sys.stderr
will be used.
<dl class="py method">
<dt class="sig sig-object py" id="logging.StreamHandler.emit">
emit(record)<a class="headerlink" href="#logging.StreamHandler.emit" title="Link to this definition">¶</a></dt>
<dd>If a formatter is specified, it is used to format the record. The record
is then written to the stream followed by <a class="reference internal" href="#logging.StreamHandler.terminator" title="logging.StreamHandler.terminator"><code class="xref py py-attr docutils literal notranslate">terminator</code></a>. If exception information
is present, it is formatted using <a class="reference internal" href="traceback.html#traceback.print_exception" title="traceback.print_exception"><code class="xref py py-func docutils literal notranslate">traceback.print_exception()</code></a> and
appended to the stream.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.StreamHandler.flush">
flush()<a class="headerlink" href="#logging.StreamHandler.flush" title="Link to this definition">¶</a></dt>
<dd>Flushes the stream by calling its <a class="reference internal" href="#logging.StreamHandler.flush" title="logging.StreamHandler.flush"><code class="xref py py-meth docutils literal notranslate">flush()</code></a> method. Note that the
<code class="xref py py-meth docutils literal notranslate">close()</code> method is inherited from <a class="reference internal" href="logging.html#logging.Handler" title="logging.Handler"><code class="xref py py-class docutils literal notranslate">Handler</code></a> and so
does no output, so an explicit <a class="reference internal" href="#logging.StreamHandler.flush" title="logging.StreamHandler.flush"><code class="xref py py-meth docutils literal notranslate">flush()</code></a> call may be needed at times.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.StreamHandler.setStream">
setStream(stream)<a class="headerlink" href="#logging.StreamHandler.setStream" title="Link to this definition">¶</a></dt>
<dd>Sets the instance’s stream to the specified value, if it is different.
The old stream is flushed before the new stream is set.
<dl class="field-list simple">
<dt class="field-odd">Parameters:</dt>
<dd class="field-odd">stream – The stream that the handler should use.
</dd>
<dt class="field-even">Returns:</dt>
<dd class="field-even">the old stream, if the stream was changed, or None if it wasn’t.
</dd>
</dl>
<div class="versionadded">
New in version 3.7.
</div>
</dd></dl>

<dl class="py attribute">
<dt class="sig sig-object py" id="logging.StreamHandler.terminator">
terminator<a class="headerlink" href="#logging.StreamHandler.terminator" title="Link to this definition">¶</a></dt>
<dd>String used as the terminator when writing a formatted record to a stream.
Default value is <code class="docutils literal notranslate">'\n'</code>.
If you don’t want a newline termination, you can set the handler instance’s
<code class="docutils literal notranslate">terminator</code> attribute to the empty string.
In earlier versions, the terminator was hardcoded as <code class="docutils literal notranslate">'\n'</code>.
<div class="versionadded">
New in version 3.2.
</div>
</dd></dl>

</dd></dl>

</section>
<section id="filehandler">
<h2>FileHandler<a class="headerlink" href="#filehandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.FileHandler" title="logging.FileHandler"><code class="xref py py-class docutils literal notranslate">FileHandler</code></a> class, located in the core <a class="reference internal" href="logging.html#module-logging" title="logging: Flexible event logging system for applications."><code class="xref py py-mod docutils literal notranslate">logging</code></a> package,
sends logging output to a disk file. It inherits the output functionality from
<a class="reference internal" href="#logging.StreamHandler" title="logging.StreamHandler"><code class="xref py py-class docutils literal notranslate">StreamHandler</code></a>.
<dl class="py class">
<dt class="sig sig-object py" id="logging.FileHandler">
class logging.FileHandler(filename, mode='a', encoding=None, delay=False, errors=None)<a class="headerlink" href="#logging.FileHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.FileHandler" title="logging.FileHandler"><code class="xref py py-class docutils literal notranslate">FileHandler</code></a> class. The specified file is
opened and used as the stream for logging. If mode is not specified,
<code class="docutils literal notranslate">'a'</code> is used. If encoding is not <code class="docutils literal notranslate">None</code>, it is used to open the file
with that encoding. If delay is true, then file opening is deferred until the
first call to <a class="reference internal" href="#logging.FileHandler.emit" title="logging.FileHandler.emit"><code class="xref py py-meth docutils literal notranslate">emit()</code></a>. By default, the file grows indefinitely. If
errors is specified, it’s used to determine how encoding errors are handled.
<div class="versionchanged">
Changed in version 3.6: As well as string values, <a class="reference internal" href="pathlib.html#pathlib.Path" title="pathlib.Path"><code class="xref py py-class docutils literal notranslate">Path</code></a> objects are also accepted
for the filename argument.
</div>
<div class="versionchanged">
Changed in version 3.9: The errors parameter was added.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.FileHandler.close">
close()<a class="headerlink" href="#logging.FileHandler.close" title="Link to this definition">¶</a></dt>
<dd>Closes the file.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.FileHandler.emit">
emit(record)<a class="headerlink" href="#logging.FileHandler.emit" title="Link to this definition">¶</a></dt>
<dd>Outputs the record to the file.
Note that if the file was closed due to logging shutdown at exit and the file
mode is ‘w’, the record will not be emitted (see <a class="reference external" href="https://bugs.python.org/issue?&#64;action=redirect&amp;bpo=42378">bpo-42378</a>).
</dd></dl>

</dd></dl>

</section>
<section id="nullhandler">
<h2>NullHandler<a class="headerlink" href="#nullhandler" title="Link to this heading">¶</a></h2>
<div class="versionadded">
New in version 3.1.
</div>
The <a class="reference internal" href="#logging.NullHandler" title="logging.NullHandler"><code class="xref py py-class docutils literal notranslate">NullHandler</code></a> class, located in the core <a class="reference internal" href="logging.html#module-logging" title="logging: Flexible event logging system for applications."><code class="xref py py-mod docutils literal notranslate">logging</code></a> package,
does not do any formatting or output. It is essentially a ‘no-op’ handler
for use by library developers.
<dl class="py class">
<dt class="sig sig-object py" id="logging.NullHandler">
class logging.NullHandler<a class="headerlink" href="#logging.NullHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.NullHandler" title="logging.NullHandler"><code class="xref py py-class docutils literal notranslate">NullHandler</code></a> class.
<dl class="py method">
<dt class="sig sig-object py" id="logging.NullHandler.emit">
emit(record)<a class="headerlink" href="#logging.NullHandler.emit" title="Link to this definition">¶</a></dt>
<dd>This method does nothing.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.NullHandler.handle">
handle(record)<a class="headerlink" href="#logging.NullHandler.handle" title="Link to this definition">¶</a></dt>
<dd>This method does nothing.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.NullHandler.createLock">
createLock()<a class="headerlink" href="#logging.NullHandler.createLock" title="Link to this definition">¶</a></dt>
<dd>This method returns <code class="docutils literal notranslate">None</code> for the lock, since there is no
underlying I/O to which access needs to be serialized.
</dd></dl>

</dd></dl>

See <a class="reference internal" href="../howto/logging.html#library-config">Configuring Logging for a Library</a> for more information on how to use
<a class="reference internal" href="#logging.NullHandler" title="logging.NullHandler"><code class="xref py py-class docutils literal notranslate">NullHandler</code></a>.
</section>
<section id="watchedfilehandler">
<h2>WatchedFileHandler<a class="headerlink" href="#watchedfilehandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.handlers.WatchedFileHandler" title="logging.handlers.WatchedFileHandler"><code class="xref py py-class docutils literal notranslate">WatchedFileHandler</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a>
module, is a <code class="xref py py-class docutils literal notranslate">FileHandler</code> which watches the file it is logging to. If
the file changes, it is closed and reopened using the file name.
A file change can happen because of usage of programs such as newsyslog and
logrotate which perform log file rotation. This handler, intended for use
under Unix/Linux, watches the file to see if it has changed since the last emit.
(A file is deemed to have changed if its device or inode have changed.) If the
file has changed, the old file stream is closed, and the file opened to get a
new stream.
This handler is not appropriate for use under Windows, because under Windows
open log files cannot be moved or renamed - logging opens the files with
exclusive locks - and so there is no need for such a handler. Furthermore,
ST_INO is not supported under Windows; <a class="reference internal" href="os.html#os.stat" title="os.stat"><code class="xref py py-func docutils literal notranslate">stat()</code></a> always returns zero
for this value.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.WatchedFileHandler">
class logging.handlers.WatchedFileHandler(filename, mode='a', encoding=None, delay=False, errors=None)<a class="headerlink" href="#logging.handlers.WatchedFileHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.WatchedFileHandler" title="logging.handlers.WatchedFileHandler"><code class="xref py py-class docutils literal notranslate">WatchedFileHandler</code></a> class. The specified
file is opened and used as the stream for logging. If mode is not specified,
<code class="docutils literal notranslate">'a'</code> is used. If encoding is not <code class="docutils literal notranslate">None</code>, it is used to open the file
with that encoding. If delay is true, then file opening is deferred until the
first call to <a class="reference internal" href="#logging.handlers.WatchedFileHandler.emit" title="logging.handlers.WatchedFileHandler.emit"><code class="xref py py-meth docutils literal notranslate">emit()</code></a>. By default, the file grows indefinitely. If
errors is provided, it determines how encoding errors are handled.
<div class="versionchanged">
Changed in version 3.6: As well as string values, <a class="reference internal" href="pathlib.html#pathlib.Path" title="pathlib.Path"><code class="xref py py-class docutils literal notranslate">Path</code></a> objects are also accepted
for the filename argument.
</div>
<div class="versionchanged">
Changed in version 3.9: The errors parameter was added.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.WatchedFileHandler.reopenIfNeeded">
reopenIfNeeded()<a class="headerlink" href="#logging.handlers.WatchedFileHandler.reopenIfNeeded" title="Link to this definition">¶</a></dt>
<dd>Checks to see if the file has changed. If it has, the existing stream is
flushed and closed and the file opened again, typically as a precursor to
outputting the record to the file.
<div class="versionadded">
New in version 3.6.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.WatchedFileHandler.emit">
emit(record)<a class="headerlink" href="#logging.handlers.WatchedFileHandler.emit" title="Link to this definition">¶</a></dt>
<dd>Outputs the record to the file, but first calls <a class="reference internal" href="#logging.handlers.WatchedFileHandler.reopenIfNeeded" title="logging.handlers.WatchedFileHandler.reopenIfNeeded"><code class="xref py py-meth docutils literal notranslate">reopenIfNeeded()</code></a> to
reopen the file if it has changed.
</dd></dl>

</dd></dl>

</section>
<section id="baserotatinghandler">
<h2>BaseRotatingHandler<a class="headerlink" href="#baserotatinghandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.handlers.BaseRotatingHandler" title="logging.handlers.BaseRotatingHandler"><code class="xref py py-class docutils literal notranslate">BaseRotatingHandler</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a>
module, is the base class for the rotating file handlers,
<a class="reference internal" href="#logging.handlers.RotatingFileHandler" title="logging.handlers.RotatingFileHandler"><code class="xref py py-class docutils literal notranslate">RotatingFileHandler</code></a> and <a class="reference internal" href="#logging.handlers.TimedRotatingFileHandler" title="logging.handlers.TimedRotatingFileHandler"><code class="xref py py-class docutils literal notranslate">TimedRotatingFileHandler</code></a>. You should
not need to instantiate this class, but it has attributes and methods you may
need to override.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.BaseRotatingHandler">
class logging.handlers.BaseRotatingHandler(filename, mode, encoding=None, delay=False, errors=None)<a class="headerlink" href="#logging.handlers.BaseRotatingHandler" title="Link to this definition">¶</a></dt>
<dd>The parameters are as for <code class="xref py py-class docutils literal notranslate">FileHandler</code>. The attributes are:
<dl class="py attribute">
<dt class="sig sig-object py" id="logging.handlers.BaseRotatingHandler.namer">
namer<a class="headerlink" href="#logging.handlers.BaseRotatingHandler.namer" title="Link to this definition">¶</a></dt>
<dd>If this attribute is set to a callable, the <a class="reference internal" href="#logging.handlers.BaseRotatingHandler.rotation_filename" title="logging.handlers.BaseRotatingHandler.rotation_filename"><code class="xref py py-meth docutils literal notranslate">rotation_filename()</code></a>
method delegates to this callable. The parameters passed to the callable
are those passed to <a class="reference internal" href="#logging.handlers.BaseRotatingHandler.rotation_filename" title="logging.handlers.BaseRotatingHandler.rotation_filename"><code class="xref py py-meth docutils literal notranslate">rotation_filename()</code></a>.
<div class="admonition note">
Note
The namer function is called quite a few times during rollover,
so it should be as simple and as fast as possible. It should also
return the same output every time for a given input, otherwise the
rollover behaviour may not work as expected.
It’s also worth noting that care should be taken when using a namer to
preserve certain attributes in the filename which are used during rotation.
For example, <a class="reference internal" href="#logging.handlers.RotatingFileHandler" title="logging.handlers.RotatingFileHandler"><code class="xref py py-class docutils literal notranslate">RotatingFileHandler</code></a> expects to have a set of log files
whose names contain successive integers, so that rotation works as expected,
and <a class="reference internal" href="#logging.handlers.TimedRotatingFileHandler" title="logging.handlers.TimedRotatingFileHandler"><code class="xref py py-class docutils literal notranslate">TimedRotatingFileHandler</code></a> deletes old log files (based on the
<code class="docutils literal notranslate">backupCount</code> parameter passed to the handler’s initializer) by determining
the oldest files to delete. For this to happen, the filenames should be
sortable using the date/time portion of the filename, and a namer needs to
respect this. (If a namer is wanted that doesn’t respect this scheme, it will
need to be used in a subclass of <a class="reference internal" href="#logging.handlers.TimedRotatingFileHandler" title="logging.handlers.TimedRotatingFileHandler"><code class="xref py py-class docutils literal notranslate">TimedRotatingFileHandler</code></a> which
overrides the <a class="reference internal" href="#logging.handlers.TimedRotatingFileHandler.getFilesToDelete" title="logging.handlers.TimedRotatingFileHandler.getFilesToDelete"><code class="xref py py-meth docutils literal notranslate">getFilesToDelete()</code></a> method to
fit in with the custom naming scheme.)
</div>
<div class="versionadded">
New in version 3.3.
</div>
</dd></dl>

<dl class="py attribute">
<dt class="sig sig-object py" id="logging.handlers.BaseRotatingHandler.rotator">
rotator<a class="headerlink" href="#logging.handlers.BaseRotatingHandler.rotator" title="Link to this definition">¶</a></dt>
<dd>If this attribute is set to a callable, the <a class="reference internal" href="#logging.handlers.BaseRotatingHandler.rotate" title="logging.handlers.BaseRotatingHandler.rotate"><code class="xref py py-meth docutils literal notranslate">rotate()</code></a> method
delegates to this callable. The parameters passed to the callable are
those passed to <a class="reference internal" href="#logging.handlers.BaseRotatingHandler.rotate" title="logging.handlers.BaseRotatingHandler.rotate"><code class="xref py py-meth docutils literal notranslate">rotate()</code></a>.
<div class="versionadded">
New in version 3.3.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.BaseRotatingHandler.rotation_filename">
rotation_filename(default_name)<a class="headerlink" href="#logging.handlers.BaseRotatingHandler.rotation_filename" title="Link to this definition">¶</a></dt>
<dd>Modify the filename of a log file when rotating.
This is provided so that a custom filename can be provided.
The default implementation calls the ‘namer’ attribute of the handler,
if it’s callable, passing the default name to it. If the attribute isn’t
callable (the default is <code class="docutils literal notranslate">None</code>), the name is returned unchanged.
<dl class="field-list simple">
<dt class="field-odd">Parameters:</dt>
<dd class="field-odd">default_name – The default name for the log file.
</dd>
</dl>
<div class="versionadded">
New in version 3.3.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.BaseRotatingHandler.rotate">
rotate(source, dest)<a class="headerlink" href="#logging.handlers.BaseRotatingHandler.rotate" title="Link to this definition">¶</a></dt>
<dd>When rotating, rotate the current log.
The default implementation calls the ‘rotator’ attribute of the handler,
if it’s callable, passing the source and dest arguments to it. If the
attribute isn’t callable (the default is <code class="docutils literal notranslate">None</code>), the source is simply
renamed to the destination.
<dl class="field-list simple">
<dt class="field-odd">Parameters:</dt>
<dd class="field-odd"><ul class="simple">
<li>source – The source filename. This is normally the base
filename, e.g. ‘test.log’.</li>
<li>dest – The destination filename. This is normally
what the source is rotated to, e.g. ‘test.log.1’.</li>
</ul>
</dd>
</dl>
<div class="versionadded">
New in version 3.3.
</div>
</dd></dl>

</dd></dl>

The reason the attributes exist is to save you having to subclass - you can use
the same callables for instances of <a class="reference internal" href="#logging.handlers.RotatingFileHandler" title="logging.handlers.RotatingFileHandler"><code class="xref py py-class docutils literal notranslate">RotatingFileHandler</code></a> and
<a class="reference internal" href="#logging.handlers.TimedRotatingFileHandler" title="logging.handlers.TimedRotatingFileHandler"><code class="xref py py-class docutils literal notranslate">TimedRotatingFileHandler</code></a>. If either the namer or rotator callable
raises an exception, this will be handled in the same way as any other
exception during an <code class="xref py py-meth docutils literal notranslate">emit()</code> call, i.e. via the <code class="xref py py-meth docutils literal notranslate">handleError()</code> method
of the handler.
If you need to make more significant changes to rotation processing, you can
override the methods.
For an example, see <a class="reference internal" href="../howto/logging-cookbook.html#cookbook-rotator-namer">Using a rotator and namer to customize log rotation processing</a>.
</section>
<section id="rotatingfilehandler">
<h2>RotatingFileHandler<a class="headerlink" href="#rotatingfilehandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.handlers.RotatingFileHandler" title="logging.handlers.RotatingFileHandler"><code class="xref py py-class docutils literal notranslate">RotatingFileHandler</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a>
module, supports rotation of disk log files.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.RotatingFileHandler">
class logging.handlers.RotatingFileHandler(filename, mode='a', maxBytes=0, backupCount=0, encoding=None, delay=False, errors=None)<a class="headerlink" href="#logging.handlers.RotatingFileHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.RotatingFileHandler" title="logging.handlers.RotatingFileHandler"><code class="xref py py-class docutils literal notranslate">RotatingFileHandler</code></a> class. The specified
file is opened and used as the stream for logging. If mode is not specified,
<code class="docutils literal notranslate">'a'</code> is used. If encoding is not <code class="docutils literal notranslate">None</code>, it is used to open the file
with that encoding. If delay is true, then file opening is deferred until the
first call to <a class="reference internal" href="#logging.handlers.RotatingFileHandler.emit" title="logging.handlers.RotatingFileHandler.emit"><code class="xref py py-meth docutils literal notranslate">emit()</code></a>. By default, the file grows indefinitely. If
errors is provided, it determines how encoding errors are handled.
You can use the maxBytes and backupCount values to allow the file to
rollover at a predetermined size. When the size is about to be exceeded,
the file is closed and a new file is silently opened for output. Rollover occurs
whenever the current log file is nearly maxBytes in length; but if either of
maxBytes or backupCount is zero, rollover never occurs, so you generally want
to set backupCount to at least 1, and have a non-zero maxBytes.
When backupCount is non-zero, the system will save old log files by appending
the extensions ‘.1’, ‘.2’ etc., to the filename. For example, with a backupCount
of 5 and a base file name of <code class="file docutils literal notranslate">app.log</code>, you would get <code class="file docutils literal notranslate">app.log</code>,
<code class="file docutils literal notranslate">app.log.1</code>, <code class="file docutils literal notranslate">app.log.2</code>, up to <code class="file docutils literal notranslate">app.log.5</code>. The file being
written to is always <code class="file docutils literal notranslate">app.log</code>. When this file is filled, it is closed
and renamed to <code class="file docutils literal notranslate">app.log.1</code>, and if files <code class="file docutils literal notranslate">app.log.1</code>,
<code class="file docutils literal notranslate">app.log.2</code>, etc. exist, then they are renamed to <code class="file docutils literal notranslate">app.log.2</code>,
<code class="file docutils literal notranslate">app.log.3</code> etc. respectively.
<div class="versionchanged">
Changed in version 3.6: As well as string values, <a class="reference internal" href="pathlib.html#pathlib.Path" title="pathlib.Path"><code class="xref py py-class docutils literal notranslate">Path</code></a> objects are also accepted
for the filename argument.
</div>
<div class="versionchanged">
Changed in version 3.9: The errors parameter was added.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.RotatingFileHandler.doRollover">
doRollover()<a class="headerlink" href="#logging.handlers.RotatingFileHandler.doRollover" title="Link to this definition">¶</a></dt>
<dd>Does a rollover, as described above.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.RotatingFileHandler.emit">
emit(record)<a class="headerlink" href="#logging.handlers.RotatingFileHandler.emit" title="Link to this definition">¶</a></dt>
<dd>Outputs the record to the file, catering for rollover as described
previously.
</dd></dl>

</dd></dl>

</section>
<section id="timedrotatingfilehandler">
<h2>TimedRotatingFileHandler<a class="headerlink" href="#timedrotatingfilehandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.handlers.TimedRotatingFileHandler" title="logging.handlers.TimedRotatingFileHandler"><code class="xref py py-class docutils literal notranslate">TimedRotatingFileHandler</code></a> class, located in the
<a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a> module, supports rotation of disk log files at certain
timed intervals.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.TimedRotatingFileHandler">
class logging.handlers.TimedRotatingFileHandler(filename, when='h', interval=1, backupCount=0, encoding=None, delay=False, utc=False, atTime=None, errors=None)<a class="headerlink" href="#logging.handlers.TimedRotatingFileHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.TimedRotatingFileHandler" title="logging.handlers.TimedRotatingFileHandler"><code class="xref py py-class docutils literal notranslate">TimedRotatingFileHandler</code></a> class. The
specified file is opened and used as the stream for logging. On rotating it also
sets the filename suffix. Rotating happens based on the product of when and
interval.
You can use the when to specify the type of interval. The list of possible
values is below. Note that they are not case sensitive.
<table class="docutils align-default">
<thead>
<tr class="row-odd"><th class="head">Value</th>
<th class="head">Type of interval</th>
<th class="head">If/how atTime is used</th>
</tr>
</thead>
<tbody>
<tr class="row-even"><td><code class="docutils literal notranslate">'S'</code></td>
<td>Seconds</td>
<td>Ignored</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">'M'</code></td>
<td>Minutes</td>
<td>Ignored</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">'H'</code></td>
<td>Hours</td>
<td>Ignored</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">'D'</code></td>
<td>Days</td>
<td>Ignored</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">'W0'-'W6'</code></td>
<td>Weekday (0=Monday)</td>
<td>Used to compute initial
rollover time</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">'midnight'</code></td>
<td>Roll over at midnight, if
atTime not specified,
else at time atTime</td>
<td>Used to compute initial
rollover time</td>
</tr>
</tbody>
</table>
When using weekday-based rotation, specify ‘W0’ for Monday, ‘W1’ for
Tuesday, and so on up to ‘W6’ for Sunday. In this case, the value passed for
interval isn’t used.
The system will save old log files by appending extensions to the filename.
The extensions are date-and-time based, using the strftime format
<code class="docutils literal notranslate">%Y-%m-%d_%H-%M-%S</code> or a leading portion thereof, depending on the
rollover interval.
When computing the next rollover time for the first time (when the handler
is created), the last modification time of an existing log file, or else
the current time, is used to compute when the next rotation will occur.
If the utc argument is true, times in UTC will be used; otherwise
local time is used.
If backupCount is nonzero, at most backupCount files
will be kept, and if more would be created when rollover occurs, the oldest
one is deleted. The deletion logic uses the interval to determine which
files to delete, so changing the interval may leave old files lying around.
If delay is true, then file opening is deferred until the first call to
<a class="reference internal" href="#logging.handlers.TimedRotatingFileHandler.emit" title="logging.handlers.TimedRotatingFileHandler.emit"><code class="xref py py-meth docutils literal notranslate">emit()</code></a>.
If atTime is not <code class="docutils literal notranslate">None</code>, it must be a <code class="docutils literal notranslate">datetime.time</code> instance which
specifies the time of day when rollover occurs, for the cases where rollover
is set to happen “at midnight” or “on a particular weekday”. Note that in
these cases, the atTime value is effectively used to compute the initial
rollover, and subsequent rollovers would be calculated via the normal
interval calculation.
If errors is specified, it’s used to determine how encoding errors are
handled.
<div class="admonition note">
Note
Calculation of the initial rollover time is done when the handler
is initialised. Calculation of subsequent rollover times is done only
when rollover occurs, and rollover occurs only when emitting output. If
this is not kept in mind, it might lead to some confusion. For example,
if an interval of “every minute” is set, that does not mean you will
always see log files with times (in the filename) separated by a minute;
if, during application execution, logging output is generated more
frequently than once a minute, then you can expect to see log files
with times separated by a minute. If, on the other hand, logging messages
are only output once every five minutes (say), then there will be gaps in
the file times corresponding to the minutes where no output (and hence no
rollover) occurred.
</div>
<div class="versionchanged">
Changed in version 3.4: atTime parameter was added.
</div>
<div class="versionchanged">
Changed in version 3.6: As well as string values, <a class="reference internal" href="pathlib.html#pathlib.Path" title="pathlib.Path"><code class="xref py py-class docutils literal notranslate">Path</code></a> objects are also accepted
for the filename argument.
</div>
<div class="versionchanged">
Changed in version 3.9: The errors parameter was added.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.TimedRotatingFileHandler.doRollover">
doRollover()<a class="headerlink" href="#logging.handlers.TimedRotatingFileHandler.doRollover" title="Link to this definition">¶</a></dt>
<dd>Does a rollover, as described above.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.TimedRotatingFileHandler.emit">
emit(record)<a class="headerlink" href="#logging.handlers.TimedRotatingFileHandler.emit" title="Link to this definition">¶</a></dt>
<dd>Outputs the record to the file, catering for rollover as described above.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.TimedRotatingFileHandler.getFilesToDelete">
getFilesToDelete()<a class="headerlink" href="#logging.handlers.TimedRotatingFileHandler.getFilesToDelete" title="Link to this definition">¶</a></dt>
<dd>Returns a list of filenames which should be deleted as part of rollover. These
are the absolute paths of the oldest backup log files written by the handler.
</dd></dl>

</dd></dl>

</section>
<section id="sockethandler">
<h2>SocketHandler<a class="headerlink" href="#sockethandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.handlers.SocketHandler" title="logging.handlers.SocketHandler"><code class="xref py py-class docutils literal notranslate">SocketHandler</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a> module,
sends logging output to a network socket. The base class uses a TCP socket.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.SocketHandler">
class logging.handlers.SocketHandler(host, port)<a class="headerlink" href="#logging.handlers.SocketHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.SocketHandler" title="logging.handlers.SocketHandler"><code class="xref py py-class docutils literal notranslate">SocketHandler</code></a> class intended to
communicate with a remote machine whose address is given by host and port.
<div class="versionchanged">
Changed in version 3.4: If <code class="docutils literal notranslate">port</code> is specified as <code class="docutils literal notranslate">None</code>, a Unix domain socket is created
using the value in <code class="docutils literal notranslate">host</code> - otherwise, a TCP socket is created.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SocketHandler.close">
close()<a class="headerlink" href="#logging.handlers.SocketHandler.close" title="Link to this definition">¶</a></dt>
<dd>Closes the socket.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SocketHandler.emit">
emit()<a class="headerlink" href="#logging.handlers.SocketHandler.emit" title="Link to this definition">¶</a></dt>
<dd>Pickles the record’s attribute dictionary and writes it to the socket in
binary format. If there is an error with the socket, silently drops the
packet. If the connection was previously lost, re-establishes the
connection. To unpickle the record at the receiving end into a
<a class="reference internal" href="logging.html#logging.LogRecord" title="logging.LogRecord"><code class="xref py py-class docutils literal notranslate">LogRecord</code></a>, use the <a class="reference internal" href="logging.html#logging.makeLogRecord" title="logging.makeLogRecord"><code class="xref py py-func docutils literal notranslate">makeLogRecord()</code></a>
function.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SocketHandler.handleError">
handleError()<a class="headerlink" href="#logging.handlers.SocketHandler.handleError" title="Link to this definition">¶</a></dt>
<dd>Handles an error which has occurred during <a class="reference internal" href="#logging.handlers.SocketHandler.emit" title="logging.handlers.SocketHandler.emit"><code class="xref py py-meth docutils literal notranslate">emit()</code></a>. The most likely
cause is a lost connection. Closes the socket so that we can retry on the
next event.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SocketHandler.makeSocket">
makeSocket()<a class="headerlink" href="#logging.handlers.SocketHandler.makeSocket" title="Link to this definition">¶</a></dt>
<dd>This is a factory method which allows subclasses to define the precise
type of socket they want. The default implementation creates a TCP socket
(<a class="reference internal" href="socket.html#socket.SOCK_STREAM" title="socket.SOCK_STREAM"><code class="xref py py-const docutils literal notranslate">socket.SOCK_STREAM</code></a>).
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SocketHandler.makePickle">
makePickle(record)<a class="headerlink" href="#logging.handlers.SocketHandler.makePickle" title="Link to this definition">¶</a></dt>
<dd>Pickles the record’s attribute dictionary in binary format with a length
prefix, and returns it ready for transmission across the socket. The
details of this operation are equivalent to:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>data = pickle.dumps(record_attr_dict, 1)
datalen = struct.pack(&#39;&gt;L&#39;, len(data))
return datalen + data
</pre></div>
</div>
Note that pickles aren’t completely secure. If you are concerned about
security, you may want to override this method to implement a more secure
mechanism. For example, you can sign pickles using HMAC and then verify
them on the receiving end, or alternatively you can disable unpickling of
global objects on the receiving end.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SocketHandler.send">
send(packet)<a class="headerlink" href="#logging.handlers.SocketHandler.send" title="Link to this definition">¶</a></dt>
<dd>Send a pickled byte-string packet to the socket. The format of the sent
byte-string is as described in the documentation for
<a class="reference internal" href="#logging.handlers.SocketHandler.makePickle" title="logging.handlers.SocketHandler.makePickle"><code class="xref py py-meth docutils literal notranslate">makePickle()</code></a>.
This function allows for partial sends, which can happen when the network
is busy.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SocketHandler.createSocket">
createSocket()<a class="headerlink" href="#logging.handlers.SocketHandler.createSocket" title="Link to this definition">¶</a></dt>
<dd>Tries to create a socket; on failure, uses an exponential back-off
algorithm. On initial failure, the handler will drop the message it was
trying to send. When subsequent messages are handled by the same
instance, it will not try connecting until some time has passed. The
default parameters are such that the initial delay is one second, and if
after that delay the connection still can’t be made, the handler will
double the delay each time up to a maximum of 30 seconds.
This behaviour is controlled by the following handler attributes:
<ul class="simple">
<li><code class="docutils literal notranslate">retryStart</code> (initial delay, defaulting to 1.0 seconds).</li>
<li><code class="docutils literal notranslate">retryFactor</code> (multiplier, defaulting to 2.0).</li>
<li><code class="docutils literal notranslate">retryMax</code> (maximum delay, defaulting to 30.0 seconds).</li>
</ul>
This means that if the remote listener starts up after the handler has
been used, you could lose messages (since the handler won’t even attempt
a connection until the delay has elapsed, but just silently drop messages
during the delay period).
</dd></dl>

</dd></dl>

</section>
<section id="datagramhandler">
<h2>DatagramHandler<a class="headerlink" href="#datagramhandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.handlers.DatagramHandler" title="logging.handlers.DatagramHandler"><code class="xref py py-class docutils literal notranslate">DatagramHandler</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a>
module, inherits from <a class="reference internal" href="#logging.handlers.SocketHandler" title="logging.handlers.SocketHandler"><code class="xref py py-class docutils literal notranslate">SocketHandler</code></a> to support sending logging messages
over UDP sockets.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.DatagramHandler">
class logging.handlers.DatagramHandler(host, port)<a class="headerlink" href="#logging.handlers.DatagramHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.DatagramHandler" title="logging.handlers.DatagramHandler"><code class="xref py py-class docutils literal notranslate">DatagramHandler</code></a> class intended to
communicate with a remote machine whose address is given by host and port.
<div class="admonition note">
Note
As UDP is not a streaming protocol, there is no persistent connection
between an instance of this handler and host. For this reason, when using a
network socket, a DNS lookup might have to be made each time an event is
logged, which can introduce some latency into the system. If this affects you,
you can do a lookup yourself and initialize this handler using the looked-up IP
address rather than the hostname.
</div>
<div class="versionchanged">
Changed in version 3.4: If <code class="docutils literal notranslate">port</code> is specified as <code class="docutils literal notranslate">None</code>, a Unix domain socket is created
using the value in <code class="docutils literal notranslate">host</code> - otherwise, a UDP socket is created.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.DatagramHandler.emit">
emit()<a class="headerlink" href="#logging.handlers.DatagramHandler.emit" title="Link to this definition">¶</a></dt>
<dd>Pickles the record’s attribute dictionary and writes it to the socket in
binary format. If there is an error with the socket, silently drops the
packet. To unpickle the record at the receiving end into a
<a class="reference internal" href="logging.html#logging.LogRecord" title="logging.LogRecord"><code class="xref py py-class docutils literal notranslate">LogRecord</code></a>, use the <a class="reference internal" href="logging.html#logging.makeLogRecord" title="logging.makeLogRecord"><code class="xref py py-func docutils literal notranslate">makeLogRecord()</code></a>
function.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.DatagramHandler.makeSocket">
makeSocket()<a class="headerlink" href="#logging.handlers.DatagramHandler.makeSocket" title="Link to this definition">¶</a></dt>
<dd>The factory method of <a class="reference internal" href="#logging.handlers.SocketHandler" title="logging.handlers.SocketHandler"><code class="xref py py-class docutils literal notranslate">SocketHandler</code></a> is here overridden to create
a UDP socket (<a class="reference internal" href="socket.html#socket.SOCK_DGRAM" title="socket.SOCK_DGRAM"><code class="xref py py-const docutils literal notranslate">socket.SOCK_DGRAM</code></a>).
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.DatagramHandler.send">
send(s)<a class="headerlink" href="#logging.handlers.DatagramHandler.send" title="Link to this definition">¶</a></dt>
<dd>Send a pickled byte-string to a socket. The format of the sent byte-string
is as described in the documentation for <a class="reference internal" href="#logging.handlers.SocketHandler.makePickle" title="logging.handlers.SocketHandler.makePickle"><code class="xref py py-meth docutils literal notranslate">SocketHandler.makePickle()</code></a>.
</dd></dl>

</dd></dl>

</section>
<section id="sysloghandler">
<h2>SysLogHandler<a class="headerlink" href="#sysloghandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.handlers.SysLogHandler" title="logging.handlers.SysLogHandler"><code class="xref py py-class docutils literal notranslate">SysLogHandler</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a> module,
supports sending logging messages to a remote or local Unix syslog.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.SysLogHandler">
class logging.handlers.SysLogHandler(address=('localhost', SYSLOG_UDP_PORT), facility=LOG_USER, socktype=socket.SOCK_DGRAM)<a class="headerlink" href="#logging.handlers.SysLogHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.SysLogHandler" title="logging.handlers.SysLogHandler"><code class="xref py py-class docutils literal notranslate">SysLogHandler</code></a> class intended to
communicate with a remote Unix machine whose address is given by address in
the form of a <code class="docutils literal notranslate">(host, port)</code> tuple. If address is not specified,
<code class="docutils literal notranslate">('localhost', 514)</code> is used. The address is used to open a socket. An
alternative to providing a <code class="docutils literal notranslate">(host, port)</code> tuple is providing an address as a
string, for example ‘/dev/log’. In this case, a Unix domain socket is used to
send the message to the syslog. If facility is not specified,
<code class="xref py py-const docutils literal notranslate">LOG_USER</code> is used. The type of socket opened depends on the
socktype argument, which defaults to <a class="reference internal" href="socket.html#socket.SOCK_DGRAM" title="socket.SOCK_DGRAM"><code class="xref py py-const docutils literal notranslate">socket.SOCK_DGRAM</code></a> and thus
opens a UDP socket. To open a TCP socket (for use with the newer syslog
daemons such as rsyslog), specify a value of <a class="reference internal" href="socket.html#socket.SOCK_STREAM" title="socket.SOCK_STREAM"><code class="xref py py-const docutils literal notranslate">socket.SOCK_STREAM</code></a>.
Note that if your server is not listening on UDP port 514,
<a class="reference internal" href="#logging.handlers.SysLogHandler" title="logging.handlers.SysLogHandler"><code class="xref py py-class docutils literal notranslate">SysLogHandler</code></a> may appear not to work. In that case, check what
address you should be using for a domain socket - it’s system dependent.
For example, on Linux it’s usually ‘/dev/log’ but on OS/X it’s
‘/var/run/syslog’. You’ll need to check your platform and use the
appropriate address (you may need to do this check at runtime if your
application needs to run on several platforms). On Windows, you pretty
much have to use the UDP option.
<div class="admonition note">
Note
On macOS 12.x (Monterey), Apple has changed the behaviour of their
syslog daemon - it no longer listens on a domain socket. Therefore, you cannot
expect <a class="reference internal" href="#logging.handlers.SysLogHandler" title="logging.handlers.SysLogHandler"><code class="xref py py-class docutils literal notranslate">SysLogHandler</code></a> to work on this system.
See <a class="reference external" href="https://github.com/python/cpython/issues/91070">gh-91070</a> for more information.
</div>
<div class="versionchanged">
Changed in version 3.2: socktype was added.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SysLogHandler.close">
close()<a class="headerlink" href="#logging.handlers.SysLogHandler.close" title="Link to this definition">¶</a></dt>
<dd>Closes the socket to the remote host.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SysLogHandler.createSocket">
createSocket()<a class="headerlink" href="#logging.handlers.SysLogHandler.createSocket" title="Link to this definition">¶</a></dt>
<dd>Tries to create a socket and, if it’s not a datagram socket, connect it
to the other end. This method is called during handler initialization,
but it’s not regarded as an error if the other end isn’t listening at
this point - the method will be called again when emitting an event, if
there is no socket at that point.
<div class="versionadded">
New in version 3.11.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SysLogHandler.emit">
emit(record)<a class="headerlink" href="#logging.handlers.SysLogHandler.emit" title="Link to this definition">¶</a></dt>
<dd>The record is formatted, and then sent to the syslog server. If exception
information is present, it is not sent to the server.
<div class="versionchanged">
Changed in version 3.2.1: (See: <a class="reference external" href="https://bugs.python.org/issue?&#64;action=redirect&amp;bpo=12168">bpo-12168</a>.) In earlier versions, the message sent to the
syslog daemons was always terminated with a NUL byte, because early
versions of these daemons expected a NUL terminated message - even
though it’s not in the relevant specification (<a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc5424.html">RFC 5424</a>). More recent
versions of these daemons don’t expect the NUL byte but strip it off
if it’s there, and even more recent daemons (which adhere more closely
to RFC 5424) pass the NUL byte on as part of the message.
To enable easier handling of syslog messages in the face of all these
differing daemon behaviours, the appending of the NUL byte has been
made configurable, through the use of a class-level attribute,
<code class="docutils literal notranslate">append_nul</code>. This defaults to <code class="docutils literal notranslate">True</code> (preserving the existing
behaviour) but can be set to <code class="docutils literal notranslate">False</code> on a <code class="docutils literal notranslate">SysLogHandler</code> instance
in order for that instance to not append the NUL terminator.
</div>
<div class="versionchanged">
Changed in version 3.3: (See: <a class="reference external" href="https://bugs.python.org/issue?&#64;action=redirect&amp;bpo=12419">bpo-12419</a>.) In earlier versions, there was no facility for
an “ident” or “tag” prefix to identify the source of the message. This
can now be specified using a class-level attribute, defaulting to
<code class="docutils literal notranslate">&quot;&quot;</code> to preserve existing behaviour, but which can be overridden on
a <code class="docutils literal notranslate">SysLogHandler</code> instance in order for that instance to prepend
the ident to every message handled. Note that the provided ident must
be text, not bytes, and is prepended to the message exactly as is.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SysLogHandler.encodePriority">
encodePriority(facility, priority)<a class="headerlink" href="#logging.handlers.SysLogHandler.encodePriority" title="Link to this definition">¶</a></dt>
<dd>Encodes the facility and priority into an integer. You can pass in strings
or integers - if strings are passed, internal mapping dictionaries are
used to convert them to integers.
The symbolic <code class="docutils literal notranslate">LOG_</code> values are defined in <a class="reference internal" href="#logging.handlers.SysLogHandler" title="logging.handlers.SysLogHandler"><code class="xref py py-class docutils literal notranslate">SysLogHandler</code></a> and
mirror the values defined in the <code class="docutils literal notranslate">sys/syslog.h</code> header file.
Priorities
<table class="docutils align-default">
<thead>
<tr class="row-odd"><th class="head">Name (string)</th>
<th class="head">Symbolic value</th>
</tr>
</thead>
<tbody>
<tr class="row-even"><td><code class="docutils literal notranslate">alert</code></td>
<td>LOG_ALERT</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">crit</code> or <code class="docutils literal notranslate">critical</code></td>
<td>LOG_CRIT</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">debug</code></td>
<td>LOG_DEBUG</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">emerg</code> or <code class="docutils literal notranslate">panic</code></td>
<td>LOG_EMERG</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">err</code> or <code class="docutils literal notranslate">error</code></td>
<td>LOG_ERR</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">info</code></td>
<td>LOG_INFO</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">notice</code></td>
<td>LOG_NOTICE</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">warn</code> or <code class="docutils literal notranslate">warning</code></td>
<td>LOG_WARNING</td>
</tr>
</tbody>
</table>
Facilities
<table class="docutils align-default">
<thead>
<tr class="row-odd"><th class="head">Name (string)</th>
<th class="head">Symbolic value</th>
</tr>
</thead>
<tbody>
<tr class="row-even"><td><code class="docutils literal notranslate">auth</code></td>
<td>LOG_AUTH</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">authpriv</code></td>
<td>LOG_AUTHPRIV</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">cron</code></td>
<td>LOG_CRON</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">daemon</code></td>
<td>LOG_DAEMON</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">ftp</code></td>
<td>LOG_FTP</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">kern</code></td>
<td>LOG_KERN</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">lpr</code></td>
<td>LOG_LPR</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">mail</code></td>
<td>LOG_MAIL</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">news</code></td>
<td>LOG_NEWS</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">syslog</code></td>
<td>LOG_SYSLOG</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">user</code></td>
<td>LOG_USER</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">uucp</code></td>
<td>LOG_UUCP</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">local0</code></td>
<td>LOG_LOCAL0</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">local1</code></td>
<td>LOG_LOCAL1</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">local2</code></td>
<td>LOG_LOCAL2</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">local3</code></td>
<td>LOG_LOCAL3</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">local4</code></td>
<td>LOG_LOCAL4</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">local5</code></td>
<td>LOG_LOCAL5</td>
</tr>
<tr class="row-even"><td><code class="docutils literal notranslate">local6</code></td>
<td>LOG_LOCAL6</td>
</tr>
<tr class="row-odd"><td><code class="docutils literal notranslate">local7</code></td>
<td>LOG_LOCAL7</td>
</tr>
</tbody>
</table>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SysLogHandler.mapPriority">
mapPriority(levelname)<a class="headerlink" href="#logging.handlers.SysLogHandler.mapPriority" title="Link to this definition">¶</a></dt>
<dd>Maps a logging level name to a syslog priority name.
You may need to override this if you are using custom levels, or
if the default algorithm is not suitable for your needs. The
default algorithm maps <code class="docutils literal notranslate">DEBUG</code>, <code class="docutils literal notranslate">INFO</code>, <code class="docutils literal notranslate">WARNING</code>, <code class="docutils literal notranslate">ERROR</code> and
<code class="docutils literal notranslate">CRITICAL</code> to the equivalent syslog names, and all other level
names to ‘warning’.
</dd></dl>

</dd></dl>

</section>
<section id="nteventloghandler">
<h2>NTEventLogHandler<a class="headerlink" href="#nteventloghandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.handlers.NTEventLogHandler" title="logging.handlers.NTEventLogHandler"><code class="xref py py-class docutils literal notranslate">NTEventLogHandler</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a>
module, supports sending logging messages to a local Windows NT, Windows 2000 or
Windows XP event log. Before you can use it, you need Mark Hammond’s Win32
extensions for Python installed.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.NTEventLogHandler">
class logging.handlers.NTEventLogHandler(appname, dllname=None, logtype='Application')<a class="headerlink" href="#logging.handlers.NTEventLogHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.NTEventLogHandler" title="logging.handlers.NTEventLogHandler"><code class="xref py py-class docutils literal notranslate">NTEventLogHandler</code></a> class. The appname is
used to define the application name as it appears in the event log. An
appropriate registry entry is created using this name. The dllname should give
the fully qualified pathname of a .dll or .exe which contains message
definitions to hold in the log (if not specified, <code class="docutils literal notranslate">'win32service.pyd'</code> is used
- this is installed with the Win32 extensions and contains some basic
placeholder message definitions. Note that use of these placeholders will make
your event logs big, as the entire message source is held in the log. If you
want slimmer logs, you have to pass in the name of your own .dll or .exe which
contains the message definitions you want to use in the event log). The
logtype is one of <code class="docutils literal notranslate">'Application'</code>, <code class="docutils literal notranslate">'System'</code> or <code class="docutils literal notranslate">'Security'</code>, and
defaults to <code class="docutils literal notranslate">'Application'</code>.
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.NTEventLogHandler.close">
close()<a class="headerlink" href="#logging.handlers.NTEventLogHandler.close" title="Link to this definition">¶</a></dt>
<dd>At this point, you can remove the application name from the registry as a
source of event log entries. However, if you do this, you will not be able
to see the events as you intended in the Event Log Viewer - it needs to be
able to access the registry to get the .dll name. The current version does
not do this.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.NTEventLogHandler.emit">
emit(record)<a class="headerlink" href="#logging.handlers.NTEventLogHandler.emit" title="Link to this definition">¶</a></dt>
<dd>Determines the message ID, event category and event type, and then logs
the message in the NT event log.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.NTEventLogHandler.getEventCategory">
getEventCategory(record)<a class="headerlink" href="#logging.handlers.NTEventLogHandler.getEventCategory" title="Link to this definition">¶</a></dt>
<dd>Returns the event category for the record. Override this if you want to
specify your own categories. This version returns 0.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.NTEventLogHandler.getEventType">
getEventType(record)<a class="headerlink" href="#logging.handlers.NTEventLogHandler.getEventType" title="Link to this definition">¶</a></dt>
<dd>Returns the event type for the record. Override this if you want to
specify your own types. This version does a mapping using the handler’s
typemap attribute, which is set up in <code class="xref py py-meth docutils literal notranslate">__init__()</code> to a dictionary
which contains mappings for <code class="xref py py-const docutils literal notranslate">DEBUG</code>, <code class="xref py py-const docutils literal notranslate">INFO</code>,
<code class="xref py py-const docutils literal notranslate">WARNING</code>, <code class="xref py py-const docutils literal notranslate">ERROR</code> and <code class="xref py py-const docutils literal notranslate">CRITICAL</code>. If you are using
your own levels, you will either need to override this method or place a
suitable dictionary in the handler’s typemap attribute.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.NTEventLogHandler.getMessageID">
getMessageID(record)<a class="headerlink" href="#logging.handlers.NTEventLogHandler.getMessageID" title="Link to this definition">¶</a></dt>
<dd>Returns the message ID for the record. If you are using your own messages,
you could do this by having the msg passed to the logger being an ID
rather than a format string. Then, in here, you could use a dictionary
lookup to get the message ID. This version returns 1, which is the base
message ID in <code class="file docutils literal notranslate">win32service.pyd</code>.
</dd></dl>

</dd></dl>

</section>
<section id="smtphandler">
<h2>SMTPHandler<a class="headerlink" href="#smtphandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.handlers.SMTPHandler" title="logging.handlers.SMTPHandler"><code class="xref py py-class docutils literal notranslate">SMTPHandler</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a> module,
supports sending logging messages to an email address via SMTP.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.SMTPHandler">
class logging.handlers.SMTPHandler(mailhost, fromaddr, toaddrs, subject, credentials=None, secure=None, timeout=1.0)<a class="headerlink" href="#logging.handlers.SMTPHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.SMTPHandler" title="logging.handlers.SMTPHandler"><code class="xref py py-class docutils literal notranslate">SMTPHandler</code></a> class. The instance is
initialized with the from and to addresses and subject line of the email. The
toaddrs should be a list of strings. To specify a non-standard SMTP port, use
the (host, port) tuple format for the mailhost argument. If you use a string,
the standard SMTP port is used. If your SMTP server requires authentication, you
can specify a (username, password) tuple for the credentials argument.
To specify the use of a secure protocol (TLS), pass in a tuple to the
secure argument. This will only be used when authentication credentials are
supplied. The tuple should be either an empty tuple, or a single-value tuple
with the name of a keyfile, or a 2-value tuple with the names of the keyfile
and certificate file. (This tuple is passed to the
<a class="reference internal" href="smtplib.html#smtplib.SMTP.starttls" title="smtplib.SMTP.starttls"><code class="xref py py-meth docutils literal notranslate">smtplib.SMTP.starttls()</code></a> method.)
A timeout can be specified for communication with the SMTP server using the
timeout argument.
<div class="versionchanged">
Changed in version 3.3: Added the timeout parameter.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SMTPHandler.emit">
emit(record)<a class="headerlink" href="#logging.handlers.SMTPHandler.emit" title="Link to this definition">¶</a></dt>
<dd>Formats the record and sends it to the specified addressees.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.SMTPHandler.getSubject">
getSubject(record)<a class="headerlink" href="#logging.handlers.SMTPHandler.getSubject" title="Link to this definition">¶</a></dt>
<dd>If you want to specify a subject line which is record-dependent, override
this method.
</dd></dl>

</dd></dl>

</section>
<section id="memoryhandler">
<h2>MemoryHandler<a class="headerlink" href="#memoryhandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.handlers.MemoryHandler" title="logging.handlers.MemoryHandler"><code class="xref py py-class docutils literal notranslate">MemoryHandler</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a> module,
supports buffering of logging records in memory, periodically flushing them to a
target handler. Flushing occurs whenever the buffer is full, or when an
event of a certain severity or greater is seen.
<a class="reference internal" href="#logging.handlers.MemoryHandler" title="logging.handlers.MemoryHandler"><code class="xref py py-class docutils literal notranslate">MemoryHandler</code></a> is a subclass of the more general
<a class="reference internal" href="#logging.handlers.BufferingHandler" title="logging.handlers.BufferingHandler"><code class="xref py py-class docutils literal notranslate">BufferingHandler</code></a>, which is an abstract class. This buffers logging
records in memory. Whenever each record is added to the buffer, a check is made
by calling <code class="xref py py-meth docutils literal notranslate">shouldFlush()</code> to see if the buffer should be flushed. If it
should, then <code class="xref py py-meth docutils literal notranslate">flush()</code> is expected to do the flushing.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.BufferingHandler">
class logging.handlers.BufferingHandler(capacity)<a class="headerlink" href="#logging.handlers.BufferingHandler" title="Link to this definition">¶</a></dt>
<dd>Initializes the handler with a buffer of the specified capacity. Here,
capacity means the number of logging records buffered.
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.BufferingHandler.emit">
emit(record)<a class="headerlink" href="#logging.handlers.BufferingHandler.emit" title="Link to this definition">¶</a></dt>
<dd>Append the record to the buffer. If <a class="reference internal" href="#logging.handlers.BufferingHandler.shouldFlush" title="logging.handlers.BufferingHandler.shouldFlush"><code class="xref py py-meth docutils literal notranslate">shouldFlush()</code></a> returns true,
call <a class="reference internal" href="#logging.handlers.BufferingHandler.flush" title="logging.handlers.BufferingHandler.flush"><code class="xref py py-meth docutils literal notranslate">flush()</code></a> to process the buffer.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.BufferingHandler.flush">
flush()<a class="headerlink" href="#logging.handlers.BufferingHandler.flush" title="Link to this definition">¶</a></dt>
<dd>For a <a class="reference internal" href="#logging.handlers.BufferingHandler" title="logging.handlers.BufferingHandler"><code class="xref py py-class docutils literal notranslate">BufferingHandler</code></a> instance, flushing means that it sets the
buffer to an empty list. This method can be overwritten to implement more useful
flushing behavior.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.BufferingHandler.shouldFlush">
shouldFlush(record)<a class="headerlink" href="#logging.handlers.BufferingHandler.shouldFlush" title="Link to this definition">¶</a></dt>
<dd>Return <code class="docutils literal notranslate">True</code> if the buffer is up to capacity. This method can be
overridden to implement custom flushing strategies.
</dd></dl>

</dd></dl>

<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.MemoryHandler">
class logging.handlers.MemoryHandler(capacity, flushLevel=ERROR, target=None, flushOnClose=True)<a class="headerlink" href="#logging.handlers.MemoryHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.MemoryHandler" title="logging.handlers.MemoryHandler"><code class="xref py py-class docutils literal notranslate">MemoryHandler</code></a> class. The instance is
initialized with a buffer size of capacity (number of records buffered).
If flushLevel is not specified, <code class="xref py py-const docutils literal notranslate">ERROR</code> is used. If no target is
specified, the target will need to be set using <a class="reference internal" href="#logging.handlers.MemoryHandler.setTarget" title="logging.handlers.MemoryHandler.setTarget"><code class="xref py py-meth docutils literal notranslate">setTarget()</code></a> before this
handler does anything useful. If flushOnClose is specified as <code class="docutils literal notranslate">False</code>,
then the buffer is not flushed when the handler is closed. If not specified
or specified as <code class="docutils literal notranslate">True</code>, the previous behaviour of flushing the buffer will
occur when the handler is closed.
<div class="versionchanged">
Changed in version 3.6: The flushOnClose parameter was added.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.MemoryHandler.close">
close()<a class="headerlink" href="#logging.handlers.MemoryHandler.close" title="Link to this definition">¶</a></dt>
<dd>Calls <a class="reference internal" href="#logging.handlers.MemoryHandler.flush" title="logging.handlers.MemoryHandler.flush"><code class="xref py py-meth docutils literal notranslate">flush()</code></a>, sets the target to <code class="docutils literal notranslate">None</code> and clears the
buffer.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.MemoryHandler.flush">
flush()<a class="headerlink" href="#logging.handlers.MemoryHandler.flush" title="Link to this definition">¶</a></dt>
<dd>For a <a class="reference internal" href="#logging.handlers.MemoryHandler" title="logging.handlers.MemoryHandler"><code class="xref py py-class docutils literal notranslate">MemoryHandler</code></a> instance, flushing means just sending the buffered
records to the target, if there is one. The buffer is also cleared when
buffered records are sent to the target. Override if you want different behavior.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.MemoryHandler.setTarget">
setTarget(target)<a class="headerlink" href="#logging.handlers.MemoryHandler.setTarget" title="Link to this definition">¶</a></dt>
<dd>Sets the target handler for this handler.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.MemoryHandler.shouldFlush">
shouldFlush(record)<a class="headerlink" href="#logging.handlers.MemoryHandler.shouldFlush" title="Link to this definition">¶</a></dt>
<dd>Checks for buffer full or a record at the flushLevel or higher.
</dd></dl>

</dd></dl>

</section>
<section id="httphandler">
<h2>HTTPHandler<a class="headerlink" href="#httphandler" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#logging.handlers.HTTPHandler" title="logging.handlers.HTTPHandler"><code class="xref py py-class docutils literal notranslate">HTTPHandler</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a> module,
supports sending logging messages to a web server, using either <code class="docutils literal notranslate">GET</code> or
<code class="docutils literal notranslate">POST</code> semantics.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.HTTPHandler">
class logging.handlers.HTTPHandler(host, url, method='GET', secure=False, credentials=None, context=None)<a class="headerlink" href="#logging.handlers.HTTPHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.HTTPHandler" title="logging.handlers.HTTPHandler"><code class="xref py py-class docutils literal notranslate">HTTPHandler</code></a> class. The host can be
of the form <code class="docutils literal notranslate">host:port</code>, should you need to use a specific port number. If
no method is specified, <code class="docutils literal notranslate">GET</code> is used. If secure is true, a HTTPS
connection will be used. The context parameter may be set to a
<a class="reference internal" href="ssl.html#ssl.SSLContext" title="ssl.SSLContext"><code class="xref py py-class docutils literal notranslate">ssl.SSLContext</code></a> instance to configure the SSL settings used for the
HTTPS connection. If credentials is specified, it should be a 2-tuple
consisting of userid and password, which will be placed in a HTTP
‘Authorization’ header using Basic authentication. If you specify
credentials, you should also specify secure=True so that your userid and
password are not passed in cleartext across the wire.
<div class="versionchanged">
Changed in version 3.5: The context parameter was added.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.HTTPHandler.mapLogRecord">
mapLogRecord(record)<a class="headerlink" href="#logging.handlers.HTTPHandler.mapLogRecord" title="Link to this definition">¶</a></dt>
<dd>Provides a dictionary, based on <code class="docutils literal notranslate">record</code>, which is to be URL-encoded
and sent to the web server. The default implementation just returns
<code class="docutils literal notranslate">record.__dict__</code>. This method can be overridden if e.g. only a
subset of <a class="reference internal" href="logging.html#logging.LogRecord" title="logging.LogRecord"><code class="xref py py-class docutils literal notranslate">LogRecord</code></a> is to be sent to the web server, or
if more specific customization of what’s sent to the server is required.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.HTTPHandler.emit">
emit(record)<a class="headerlink" href="#logging.handlers.HTTPHandler.emit" title="Link to this definition">¶</a></dt>
<dd>Sends the record to the web server as a URL-encoded dictionary. The
<a class="reference internal" href="#logging.handlers.HTTPHandler.mapLogRecord" title="logging.handlers.HTTPHandler.mapLogRecord"><code class="xref py py-meth docutils literal notranslate">mapLogRecord()</code></a> method is used to convert the record to the
dictionary to be sent.
</dd></dl>

<div class="admonition note">
Note
Since preparing a record for sending it to a web server is not
the same as a generic formatting operation, using
<a class="reference internal" href="logging.html#logging.Handler.setFormatter" title="logging.Handler.setFormatter"><code class="xref py py-meth docutils literal notranslate">setFormatter()</code></a> to specify a
<a class="reference internal" href="logging.html#logging.Formatter" title="logging.Formatter"><code class="xref py py-class docutils literal notranslate">Formatter</code></a> for a <a class="reference internal" href="#logging.handlers.HTTPHandler" title="logging.handlers.HTTPHandler"><code class="xref py py-class docutils literal notranslate">HTTPHandler</code></a> has no effect.
Instead of calling <a class="reference internal" href="logging.html#logging.Handler.format" title="logging.Handler.format"><code class="xref py py-meth docutils literal notranslate">format()</code></a>, this handler calls
<a class="reference internal" href="#logging.handlers.HTTPHandler.mapLogRecord" title="logging.handlers.HTTPHandler.mapLogRecord"><code class="xref py py-meth docutils literal notranslate">mapLogRecord()</code></a> and then <a class="reference internal" href="urllib.parse.html#urllib.parse.urlencode" title="urllib.parse.urlencode"><code class="xref py py-func docutils literal notranslate">urllib.parse.urlencode()</code></a> to encode the
dictionary in a form suitable for sending to a web server.
</div>
</dd></dl>

</section>
<section id="queuehandler">
<h2>QueueHandler<a class="headerlink" href="#queuehandler" title="Link to this heading">¶</a></h2>
<div class="versionadded">
New in version 3.2.
</div>
The <a class="reference internal" href="#logging.handlers.QueueHandler" title="logging.handlers.QueueHandler"><code class="xref py py-class docutils literal notranslate">QueueHandler</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a> module,
supports sending logging messages to a queue, such as those implemented in the
<a class="reference internal" href="queue.html#module-queue" title="queue: A synchronized queue class."><code class="xref py py-mod docutils literal notranslate">queue</code></a> or <a class="reference internal" href="multiprocessing.html#module-multiprocessing" title="multiprocessing: Process-based parallelism."><code class="xref py py-mod docutils literal notranslate">multiprocessing</code></a> modules.
Along with the <a class="reference internal" href="#logging.handlers.QueueListener" title="logging.handlers.QueueListener"><code class="xref py py-class docutils literal notranslate">QueueListener</code></a> class, <a class="reference internal" href="#logging.handlers.QueueHandler" title="logging.handlers.QueueHandler"><code class="xref py py-class docutils literal notranslate">QueueHandler</code></a> can be used
to let handlers do their work on a separate thread from the one which does the
logging. This is important in web applications and also other service
applications where threads servicing clients need to respond as quickly as
possible, while any potentially slow operations (such as sending an email via
<a class="reference internal" href="#logging.handlers.SMTPHandler" title="logging.handlers.SMTPHandler"><code class="xref py py-class docutils literal notranslate">SMTPHandler</code></a>) are done on a separate thread.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.QueueHandler">
class logging.handlers.QueueHandler(queue)<a class="headerlink" href="#logging.handlers.QueueHandler" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.QueueHandler" title="logging.handlers.QueueHandler"><code class="xref py py-class docutils literal notranslate">QueueHandler</code></a> class. The instance is
initialized with the queue to send messages to. The queue can be any
queue-like object; it’s used as-is by the <a class="reference internal" href="#logging.handlers.QueueHandler.enqueue" title="logging.handlers.QueueHandler.enqueue"><code class="xref py py-meth docutils literal notranslate">enqueue()</code></a> method, which
needs to know how to send messages to it. The queue is not required to
have the task tracking API, which means that you can use
<a class="reference internal" href="queue.html#queue.SimpleQueue" title="queue.SimpleQueue"><code class="xref py py-class docutils literal notranslate">SimpleQueue</code></a> instances for queue.
<div class="admonition note">
Note
If you are using <a class="reference internal" href="multiprocessing.html#module-multiprocessing" title="multiprocessing: Process-based parallelism."><code class="xref py py-mod docutils literal notranslate">multiprocessing</code></a>, you should avoid using
<a class="reference internal" href="queue.html#queue.SimpleQueue" title="queue.SimpleQueue"><code class="xref py py-class docutils literal notranslate">SimpleQueue</code></a> and instead use <a class="reference internal" href="multiprocessing.html#multiprocessing.Queue" title="multiprocessing.Queue"><code class="xref py py-class docutils literal notranslate">multiprocessing.Queue</code></a>.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.QueueHandler.emit">
emit(record)<a class="headerlink" href="#logging.handlers.QueueHandler.emit" title="Link to this definition">¶</a></dt>
<dd>Enqueues the result of preparing the LogRecord. Should an exception
occur (e.g. because a bounded queue has filled up), the
<a class="reference internal" href="logging.html#logging.Handler.handleError" title="logging.Handler.handleError"><code class="xref py py-meth docutils literal notranslate">handleError()</code></a> method is called to handle the
error. This can result in the record silently being dropped (if
<a class="reference internal" href="logging.html#logging.raiseExceptions" title="logging.raiseExceptions"><code class="xref py py-data docutils literal notranslate">logging.raiseExceptions</code></a> is <code class="docutils literal notranslate">False</code>) or a message printed to
<code class="docutils literal notranslate">sys.stderr</code> (if <a class="reference internal" href="logging.html#logging.raiseExceptions" title="logging.raiseExceptions"><code class="xref py py-data docutils literal notranslate">logging.raiseExceptions</code></a> is <code class="docutils literal notranslate">True</code>).
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.QueueHandler.prepare">
prepare(record)<a class="headerlink" href="#logging.handlers.QueueHandler.prepare" title="Link to this definition">¶</a></dt>
<dd>Prepares a record for queuing. The object returned by this
method is enqueued.
The base implementation formats the record to merge the message,
arguments, exception and stack information, if present. It also removes
unpickleable items from the record in-place. Specifically, it overwrites
the record’s <code class="xref py py-attr docutils literal notranslate">msg</code> and <code class="xref py py-attr docutils literal notranslate">message</code> attributes with the merged
message (obtained by calling the handler’s <a class="reference internal" href="functions.html#format" title="format"><code class="xref py py-meth docutils literal notranslate">format()</code></a> method), and
sets the <code class="xref py py-attr docutils literal notranslate">args</code>, <code class="xref py py-attr docutils literal notranslate">exc_info</code> and <code class="xref py py-attr docutils literal notranslate">exc_text</code> attributes
to <code class="docutils literal notranslate">None</code>.
You might want to override this method if you want to convert
the record to a dict or JSON string, or send a modified copy
of the record while leaving the original intact.
<div class="admonition note">
Note
The base implementation formats the message with arguments, sets
the <code class="docutils literal notranslate">message</code> and <code class="docutils literal notranslate">msg</code> attributes to the formatted message and
sets the <code class="docutils literal notranslate">args</code> and <code class="docutils literal notranslate">exc_text</code> attributes to <code class="docutils literal notranslate">None</code> to allow
pickling and to prevent further attempts at formatting. This means
that a handler on the <a class="reference internal" href="#logging.handlers.QueueListener" title="logging.handlers.QueueListener"><code class="xref py py-class docutils literal notranslate">QueueListener</code></a> side won’t have the
information to do custom formatting, e.g. of exceptions. You may wish
to subclass <code class="docutils literal notranslate">QueueHandler</code> and override this method to e.g. avoid
setting <code class="docutils literal notranslate">exc_text</code> to <code class="docutils literal notranslate">None</code>. Note that the <code class="docutils literal notranslate">message</code> / <code class="docutils literal notranslate">msg</code>
/ <code class="docutils literal notranslate">args</code> changes are related to ensuring the record is pickleable,
and you might or might not be able to avoid doing that depending on
whether your <code class="docutils literal notranslate">args</code> are pickleable. (Note that you may have to
consider not only your own code but also code in any libraries that
you use.)
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.QueueHandler.enqueue">
enqueue(record)<a class="headerlink" href="#logging.handlers.QueueHandler.enqueue" title="Link to this definition">¶</a></dt>
<dd>Enqueues the record on the queue using <code class="docutils literal notranslate">put_nowait()</code>; you may
want to override this if you want to use blocking behaviour, or a
timeout, or a customized queue implementation.
</dd></dl>

<dl class="py attribute">
<dt class="sig sig-object py" id="logging.handlers.QueueHandler.listener">
listener<a class="headerlink" href="#logging.handlers.QueueHandler.listener" title="Link to this definition">¶</a></dt>
<dd>When created via configuration using <a class="reference internal" href="logging.config.html#logging.config.dictConfig" title="logging.config.dictConfig"><code class="xref py py-func docutils literal notranslate">dictConfig()</code></a>, this
attribute will contain a <a class="reference internal" href="#logging.handlers.QueueListener" title="logging.handlers.QueueListener"><code class="xref py py-class docutils literal notranslate">QueueListener</code></a> instance for use with this
handler. Otherwise, it will be <code class="docutils literal notranslate">None</code>.
<div class="versionadded">
New in version 3.12.
</div>
</dd></dl>

</dd></dl>

</section>
<section id="queuelistener">
<h2>QueueListener<a class="headerlink" href="#queuelistener" title="Link to this heading">¶</a></h2>
<div class="versionadded">
New in version 3.2.
</div>
The <a class="reference internal" href="#logging.handlers.QueueListener" title="logging.handlers.QueueListener"><code class="xref py py-class docutils literal notranslate">QueueListener</code></a> class, located in the <a class="reference internal" href="#module-logging.handlers" title="logging.handlers: Handlers for the logging module."><code class="xref py py-mod docutils literal notranslate">logging.handlers</code></a>
module, supports receiving logging messages from a queue, such as those
implemented in the <a class="reference internal" href="queue.html#module-queue" title="queue: A synchronized queue class."><code class="xref py py-mod docutils literal notranslate">queue</code></a> or <a class="reference internal" href="multiprocessing.html#module-multiprocessing" title="multiprocessing: Process-based parallelism."><code class="xref py py-mod docutils literal notranslate">multiprocessing</code></a> modules. The
messages are received from a queue in an internal thread and passed, on
the same thread, to one or more handlers for processing. While
<a class="reference internal" href="#logging.handlers.QueueListener" title="logging.handlers.QueueListener"><code class="xref py py-class docutils literal notranslate">QueueListener</code></a> is not itself a handler, it is documented here
because it works hand-in-hand with <a class="reference internal" href="#logging.handlers.QueueHandler" title="logging.handlers.QueueHandler"><code class="xref py py-class docutils literal notranslate">QueueHandler</code></a>.
Along with the <a class="reference internal" href="#logging.handlers.QueueHandler" title="logging.handlers.QueueHandler"><code class="xref py py-class docutils literal notranslate">QueueHandler</code></a> class, <a class="reference internal" href="#logging.handlers.QueueListener" title="logging.handlers.QueueListener"><code class="xref py py-class docutils literal notranslate">QueueListener</code></a> can be used
to let handlers do their work on a separate thread from the one which does the
logging. This is important in web applications and also other service
applications where threads servicing clients need to respond as quickly as
possible, while any potentially slow operations (such as sending an email via
<a class="reference internal" href="#logging.handlers.SMTPHandler" title="logging.handlers.SMTPHandler"><code class="xref py py-class docutils literal notranslate">SMTPHandler</code></a>) are done on a separate thread.
<dl class="py class">
<dt class="sig sig-object py" id="logging.handlers.QueueListener">
class logging.handlers.QueueListener(queue, *handlers, respect_handler_level=False)<a class="headerlink" href="#logging.handlers.QueueListener" title="Link to this definition">¶</a></dt>
<dd>Returns a new instance of the <a class="reference internal" href="#logging.handlers.QueueListener" title="logging.handlers.QueueListener"><code class="xref py py-class docutils literal notranslate">QueueListener</code></a> class. The instance is
initialized with the queue to send messages to and a list of handlers which
will handle entries placed on the queue. The queue can be any queue-like
object; it’s passed as-is to the <a class="reference internal" href="#logging.handlers.QueueListener.dequeue" title="logging.handlers.QueueListener.dequeue"><code class="xref py py-meth docutils literal notranslate">dequeue()</code></a> method, which needs
to know how to get messages from it. The queue is not required to have the
task tracking API (though it’s used if available), which means that you can
use <a class="reference internal" href="queue.html#queue.SimpleQueue" title="queue.SimpleQueue"><code class="xref py py-class docutils literal notranslate">SimpleQueue</code></a> instances for queue.
<div class="admonition note">
Note
If you are using <a class="reference internal" href="multiprocessing.html#module-multiprocessing" title="multiprocessing: Process-based parallelism."><code class="xref py py-mod docutils literal notranslate">multiprocessing</code></a>, you should avoid using
<a class="reference internal" href="queue.html#queue.SimpleQueue" title="queue.SimpleQueue"><code class="xref py py-class docutils literal notranslate">SimpleQueue</code></a> and instead use <a class="reference internal" href="multiprocessing.html#multiprocessing.Queue" title="multiprocessing.Queue"><code class="xref py py-class docutils literal notranslate">multiprocessing.Queue</code></a>.
</div>
If <code class="docutils literal notranslate">respect_handler_level</code> is <code class="docutils literal notranslate">True</code>, a handler’s level is respected
(compared with the level for the message) when deciding whether to pass
messages to that handler; otherwise, the behaviour is as in previous Python
versions - to always pass each message to each handler.
<div class="versionchanged">
Changed in version 3.5: The <code class="docutils literal notranslate">respect_handler_level</code> argument was added.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.QueueListener.dequeue">
dequeue(block)<a class="headerlink" href="#logging.handlers.QueueListener.dequeue" title="Link to this definition">¶</a></dt>
<dd>Dequeues a record and return it, optionally blocking.
The base implementation uses <code class="docutils literal notranslate">get()</code>. You may want to override this
method if you want to use timeouts or work with custom queue
implementations.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.QueueListener.prepare">
prepare(record)<a class="headerlink" href="#logging.handlers.QueueListener.prepare" title="Link to this definition">¶</a></dt>
<dd>Prepare a record for handling.
This implementation just returns the passed-in record. You may want to
override this method if you need to do any custom marshalling or
manipulation of the record before passing it to the handlers.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.QueueListener.handle">
handle(record)<a class="headerlink" href="#logging.handlers.QueueListener.handle" title="Link to this definition">¶</a></dt>
<dd>Handle a record.
This just loops through the handlers offering them the record
to handle. The actual object passed to the handlers is that which
is returned from <a class="reference internal" href="#logging.handlers.QueueListener.prepare" title="logging.handlers.QueueListener.prepare"><code class="xref py py-meth docutils literal notranslate">prepare()</code></a>.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.QueueListener.start">
start()<a class="headerlink" href="#logging.handlers.QueueListener.start" title="Link to this definition">¶</a></dt>
<dd>Starts the listener.
This starts up a background thread to monitor the queue for
LogRecords to process.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.QueueListener.stop">
stop()<a class="headerlink" href="#logging.handlers.QueueListener.stop" title="Link to this definition">¶</a></dt>
<dd>Stops the listener.
This asks the thread to terminate, and then waits for it to do so.
Note that if you don’t call this before your application exits, there
may be some records still left on the queue, which won’t be processed.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="logging.handlers.QueueListener.enqueue_sentinel">
enqueue_sentinel()<a class="headerlink" href="#logging.handlers.QueueListener.enqueue_sentinel" title="Link to this definition">¶</a></dt>
<dd>Writes a sentinel to the queue to tell the listener to quit. This
implementation uses <code class="docutils literal notranslate">put_nowait()</code>. You may want to override this
method if you want to use timeouts or work with custom queue
implementations.
<div class="versionadded">
New in version 3.3.
</div>
</dd></dl>

</dd></dl>

<div class="admonition seealso">
See also
<dl class="simple">
<dt>Module <a class="reference internal" href="logging.html#module-logging" title="logging: Flexible event logging system for applications."><code class="xref py py-mod docutils literal notranslate">logging</code></a></dt><dd>API reference for the logging module.
</dd>
<dt>Module <a class="reference internal" href="logging.config.html#module-logging.config" title="logging.config: Configuration of the logging module."><code class="xref py py-mod docutils literal notranslate">logging.config</code></a></dt><dd>Configuration API for the logging module.
</dd>
</dl>
</div>
</section>
</section>

<div class="clearer"></div>
 </div>
 </div>
 </div>
 <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
 <div class="sphinxsidebarwrapper">
 <div>
 <h3><a href="../contents.html">Table of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#"><code class="xref py py-mod docutils literal notranslate">logging.handlers</code> — Logging handlers</a><ul>
<li><a class="reference internal" href="#streamhandler">StreamHandler</a></li>
<li><a class="reference internal" href="#filehandler">FileHandler</a></li>
<li><a class="reference internal" href="#nullhandler">NullHandler</a></li>
<li><a class="reference internal" href="#watchedfilehandler">WatchedFileHandler</a></li>
<li><a class="reference internal" href="#baserotatinghandler">BaseRotatingHandler</a></li>
<li><a class="reference internal" href="#rotatingfilehandler">RotatingFileHandler</a></li>
<li><a class="reference internal" href="#timedrotatingfilehandler">TimedRotatingFileHandler</a></li>
<li><a class="reference internal" href="#sockethandler">SocketHandler</a></li>
<li><a class="reference internal" href="#datagramhandler">DatagramHandler</a></li>
<li><a class="reference internal" href="#sysloghandler">SysLogHandler</a></li>
<li><a class="reference internal" href="#nteventloghandler">NTEventLogHandler</a></li>
<li><a class="reference internal" href="#smtphandler">SMTPHandler</a></li>
<li><a class="reference internal" href="#memoryhandler">MemoryHandler</a></li>
<li><a class="reference internal" href="#httphandler">HTTPHandler</a></li>
<li><a class="reference internal" href="#queuehandler">QueueHandler</a></li>
<li><a class="reference internal" href="#queuelistener">QueueListener</a></li>
</ul>
</li>
</ul>

</div>
 <div class="clearer"></div>
 </div> 
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 >index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="getpass.html" title="getpass — Portable password input"
 >next</a> |</li>
 <li class="right" >
 <a href="logging.config.html" title="logging.config — Logging configuration"
 >previous</a> |</li>

<li class="nav-item nav-item-1"><a href="index.html" >The Python Standard Library</a> &#187;</li>
 <li class="nav-item nav-item-2"><a href="allos.html" >Generic Operating System Services</a> &#187;</li>
 <li class="nav-item nav-item-this"><a href=""><code class="xref py py-mod docutils literal notranslate">logging.handlers</code> — Logging handlers</a></li>
 <li class="right">

<div class="inline-search" role="search">
 <form class="inline-search" action="../search.html" method="get">
 <input placeholder="Quick search" aria-label="Quick search" type="search" name="q" id="search-box" />
 <input type="submit" value="Go" />
 </form>
 </div>
 |
 </li>
 <li class="right">
<label class="theme-selector-label">
 Theme
 <select class="theme-selector" oninput="activateTheme(this.value)">
 <option value="auto" selected>Auto</option>
 <option value="light">Light</option>
 <option value="dark">Dark</option>
 </select>
</label> |</li>
 
 </ul>
 </div> 
 <div class="footer">
 &copy; 
 <a href="../copyright.html">
 
 Copyright
 
 </a>
 2001-2024, Python Software Foundation.
 
 This page is licensed under the Python Software Foundation License Version 2.
 
 Examples, recipes, and other code in the documentation are additionally licensed under the Zero Clause BSD License.
 
 
 See <a href="/license.html">History and License</a> for more information.

The Python Software Foundation is a non-profit corporation.
<a href="https://www.python.org/psf/donations/">Please donate.</a>
 
 
 Last updated on Apr 09, 2024 (13:47 UTC).
 
 <a href="/bugs.html">Found a bug</a>?

Created using <a href="https://www.sphinx-doc.org/">Sphinx</a> 7.2.6.
 </div>

</body>
</html>