Django app that tracks all user requests and saves following data to database:
user
request method
response status code
IP address
URL path
GET parameters
POST data
session
language code
timezone
content type
user agent
response content (if internal server error occures)
is_secure flag
is_ajax flag
is_debug flag
created and modified timestamps
Tested on Django 1.4.5 and Django 1.8.3
Requirements
Django
Installation
Install python library using pip: pip install django-detective
Add detective to INSTALLED_APPS in your Django settings file
Add detective.middleware.TrackingMiddleware to MIDDLEWARE_CLASSES in your Django settings file
Include detective.urls in your urls.py with detective namespace
Sync your database
Settings
- DETECTIVE_SAVE_RESPONSES
If True, response data will be saved in database. Default: False.
- DETECTIVE_SAVE_ERROR_RESPONSES
If True, internal server error responses with exception (500) are stored in database. Default: True.
- DETECTIVE_TRACK_AJAX_REQUESTS
If False, ajax requests won’t be tracked. Default: True.
- DETECTIVE_TRACK_ANONYMOUS_REQUESTS
If False, anonymous requests won’t be tracked. Default: True.
1 maintainer
Metadata
1 maintainer
Release files for django-detective 0.6.3
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 | Actions |
|---|---|---|---|---|
| django-detective-0.6.3.tar.gz | 6.1 kB | Without provenance | Details for django-detective-0.6.3.tar.gz |
Release files / django-detective-0.6.3.tar.gz
| Download URL | django-detective-0.6.3.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc831070b60bd90f5914c081ac48632139cd19c61490a39d31720c7afad517ba
|
|
BLAKE2b-256 checksum How to use checksums |
75f047085a4b940e543d3a5985b91d7b5aeb3dd0005f5bb3f5ba6a7341398002
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-detective 0.6.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.
