Request Logging for WSGI Web Applications
This is a middleware which you can use to log requests to your WSGI based site. It’s even imitating Apache’s combined log format to allow you to use any of the many tools for Apache log file analysis.
By making use of Python’s standard library logging facilities, you can easily set it up to log to STDOUT, time rotated log files, email, syslog, etc.
Installation
Simply install this Python module via
pip install wsgi-request-logger
Usage
To add this middleware to your WSGI application and log to the file access.log, do:
from requestlogger import WSGILogger, ApacheFormatter
from logging.handlers import TimedRotatingFileHandler
def application(environ, start_response):
response_body = 'The request method was %s' % environ['REQUEST_METHOD']
response_body = response_body.encode('utf-8')
response_headers = [('Content-Type', 'text/plain'),
('Content-Length', str(len(response_body)))]
start_response('200 OK', response_headers)
return [response_body]
handlers = [ TimedRotatingFileHandler('access.log', 'd', 7) , ]
loggingapp = WSGILogger(application, handlers, ApacheFormatter())
if __name__ == '__main__':
from wsgiref.simple_server import make_server
http = make_server('', 8080, loggingapp)
http.serve_forever()
License
This software, wsgi-request-logger, is published under a 3-clause BSD license.
Developers’ Resources
To read about your options for the logging handler, you may want to read Python’s Logging Cookbook.
Documentation on Apache’s log format can be found here.
The WSGI - Web Server Gateway Interface - is defined in PEP 333 with an update for Python 3 in PEP 3333.
General References
The source code for this Python module is hosted on Github.
A blog post with more background information and usage examples: wsgi-request-logger – Logging HTTP Requests With Any WSGI Web Application like Flask, Bottle or Django
Metadata
Release files for wsgi-request-logger 0.4.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| wsgi-request-logger-0.4.6.tar.gz | 4.4 kB | Without provenance | Details |
Release files / wsgi-request-logger-0.4.6.tar.gz
| Download URL | wsgi-request-logger-0.4.6.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
445d7ec52799562f812006394d0b4a7064b37084c6ea6bd74ea7a2136c97ed83
|
|
BLAKE2b-256 checksum How to use checksums |
04dd5e6c52b96a841baec75e5c5647460214aa02e9c4902c7b250375352224c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for wsgi-request-logger 0.4.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.