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.
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file django-journal-1.3.0.tar.gz.
File metadata
- Download URL: django-journal-1.3.0.tar.gz
- Upload date:
- Size: 7.6 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 44fa07b616e38c60cdd36cac27244d489e4f5252c04947ac0104f20eb7692c4c |
|
| MD5 | fd41fd7681813ce49c72c5b9d12d8427 |
|
| BLAKE2b-256 | 3f25f2ef8e3c6e2d24093ce6b1effc0c83c263135fb3e5ee1640b652af115708 |
