Skip to main content

Keep a structured -- i.e. not just log strings -- journal of events in your applications

Project description

Log event to a journal. Keep details of the event linked to the event message, keep also the template for displaying the event in case we want to improve display.

To use just do:

import django_journal
django_journal.record('my-tag', '{user} did this to {that}',
           user=request.user, that=model_instance)

Admin display

admin.JournalModelAdmin recompute messages from the journal message as HTML adding links for filtering by object and to the change admin page for the object if it has one.

Recording error events

If you use transactions you must use error_record() instead of record() and set JOURNAL_DB_FOR_ERROR_ALIAS in your settings to define another db alias to use so that journal record does not happen inside the current transaction.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-journal-1.5.0.tar.gz (7.8 kB view details)

Uploaded Source

File details

Details for the file django-journal-1.5.0.tar.gz.

File metadata

File hashes

Hashes for django-journal-1.5.0.tar.gz
Algorithm Hash digest
SHA256 60d6a5ef6a2603a5bb0fb4198b230f9f6249b3c232f8e8015dc71f87cbc1f122
MD5 764d07550309211667571cb9dc969adb
BLAKE2b-256 784f1a1908bbbd33d65c4292bd03a9ff5351c82dfe99a9e18f47cb655ff3fa73

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page