Skip to main content

django-logutils

https://badge.fury.io/py/django-logutils.png https://travis-ci.org/jsmits/django-logutils.png?branch=master Documentation Status https://coveralls.io/repos/jsmits/django-logutils/badge.svg?branch=master&service=github

Various logging-related utilities for Django projects. For now, it provides a LoggingMiddleware class and an EventLogger class.

Documentation

http://django-logutils.readthedocs.org

Quickstart

Install django-logutils:

pip install django-logutils

LoggingMiddleware

LoggingMiddleware is middleware class for Django, that logs extra request-related information. To use it in your Django projects, add it to your MIDDLEWARE_CLASSES setting:

MIDDLEWARE_CLASSES = (
    ...
    'django_logutils.middleware.LoggingMiddleware',
    ...
)

The extra information consists of:

  • event (default: ‘request’)

  • remote ip address: the remote ip address of the user doing the request.

  • user email: the email address of the requesting user, if available

  • request method: post or get

  • request url path

  • response status code

  • content length of the response body

  • request time

N.B.: event can be overriden by using the LOGUTILS_LOGGING_MIDDLEWARE_EVENT setting in your project.

The log message itself is a string composed of the remote ip address, the user email, the request method, the request url, the status code, the content length of the body and the request time. Additionally, a dictionary with the log items are added as an extra keyword argument when sending a logging statement.

If settings.DEBUG is True or the request time is more than 1 second, two additional parameters are added to the logging dictionary: nr_queries that represents the number of queries executed during the request-response cycle and sql_time that represents the time it took to execute those queries. Slow requests are also raised to a loglevel of WARNING.

N.B.: the time threshold for slow requests can be overriden by using the LOGUTILS_REQUEST_TIME_THRESHOLD setting in your project.

EventLogger

The EventLogger class makes it easy to create dictionary-based logging statements, that can be used by log processors like Logstash. Log events can be used to track metrics and/or to create visualisations.

Here’s an example of how you can use it:

>>> from django_logutils.utils import EventLogger
>>> log_event = EventLogger('my_logger')
>>> log_event('my_event', {'action': 'push_button'})

Development

Install the test requirements:

$ pip install -r requirements/test.txt

Run the tests to check everything is fine:

$ make test

To run the tests and opening the coverage html in your browser:

$ make coverage

To run flake8 and pylint, do:

$ make lint

To generate the documentation, do:

$ make docs

History

0.4.3 (2017-05-11)

  • Make sure that log messages are aggregable by tools like Sentry.

0.4.2 (2015-10-30)

  • Support StreamingHttpResponse that doesn’t have content length.

0.4.1 (2015-08-21)

  • Add tests for app settings.

0.4.0 (2015-08-20)

  • Make REQUEST_TIME_THRESHOLD a setting.

0.3.1 (2015-08-04)

  • Update documentation.

0.3.0 (2015-08-04)

  • Add EventLogger class.

0.2.5 (2015-07-31)

  • Reach 100% test coverage.

0.2.4 (2015-07-31)

  • Improve project structure.

0.2.3 (2015-07-30)

  • Add log_event utility function for logging events.

0.2.2 (2015-07-29)

  • Add add_items_to_message utility function.

0.2.1 (2015-07-29)

  • More and better tests.

0.2.0 (2015-07-28)

  • Release replacing previous faulty dev release.

0.1.0 (2015-07-28)

  • First release on PyPI.

Metadata

Release files for django-logutils 0.4.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-logutils 0.4.3
File Size Uploaded Provenance
django-logutils-0.4.3.tar.gz 8.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for django-logutils 0.4.3
File Interpreter ABI Platform
django_logutils-0.4.3-py2.py3-none-any.whl Python 3, Python 2 none any Details

Total release size: 18.0 kB

Release files / django-logutils-0.4.3.tar.gz

Download URL django-logutils-0.4.3.tar.gz
Size 8.4 kB
Tags Source
SHA-256 checksum
How to use checksums
3452299c15c18bc389af950e3b247973862c165a9546e4d03b6d8c3c543fa715
BLAKE2b-256 checksum
How to use checksums
4aaab0d9bfe9c16a443723dc9c215dda5e8ad41a3116b2d9ee0b0f31c4d4f4e2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / django_logutils-0.4.3-py2.py3-none-any.whl

Download URL django_logutils-0.4.3-py2.py3-none-any.whl
Size 9.7 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
1b07f28d6ac23b4677b06a5214b2b8d1742355259ee50a919d8dd6368567e527
BLAKE2b-256 checksum
How to use checksums
062835888c1e5828dc77e81d9e7670da76a6b6f370331e073440a61293eb86f3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for django-logutils 0.4.3

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page