This Django app adds extra fields to log records emitted by the standard Python logging. Currently these include:
username - Username of the currently logged in Django user, if any. If no user is logged in the value is “_” (distinct from empty string, which means that the information is not available).
client_ip - IP address of the client browser, obtained from REMOTE_ADDR and HTTP_X_FORWARDED_FOR.
absolute_url - the absolute URL of the current request, including the query string.
raw_post_data - the raw POST data for the current request, if any.
These fields are then available to be used in your logging formatter (see example below). They are also visible in Django Sentry as additional data (if you have Django Sentry installed).
Metadata
Release files for DjangoRequestLogger 0.2.0
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 |
|---|---|---|---|---|
| DjangoRequestLogger-0.2.0.tar.gz | 4.0 kB | Without provenance | Details for DjangoRequestLogger-0.2.0.tar.gz |
Release files / DjangoRequestLogger-0.2.0.tar.gz
| Download URL | DjangoRequestLogger-0.2.0.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7762028c5292bce650dd54fdc8baf1219cd807b48191cdd2b039e1ff1c210b20
|
|
BLAKE2b-256 checksum How to use checksums |
bd6a0568fab6d944101a3e99fec0447079cfcd487591f653da75748bf26a9a07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for DjangoRequestLogger 0.2.0
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.