Django Debug Logging
Django Debug Logging is a “plugin” for the Django Debug Toolbar that allows users to log the debug toolbar statistics to the database during a site crawl. This allows users to create performance testing plans to exercise the site, and then review and aggregate the results afterwards to identify performance problems.
It also provides a basic UI for browsing the details that have been logged to the database and reviewing aggregated information about test runs. The UI borrows a lot from the custom Sphinx theme by the Read the Docs team, and the Sentry project from Disqus.
The overall goal is to use this tool to monitor performance statistics over time, so that you can see trends and spikes in the number of queries, cache misses, cpu time, etc., and identify where in the app the problems are coming from. It is not intended as a load testing tool, so features like concurrency and warmup periods will not be part of the initial focus.
Screenshots
The main Debug Logging frontend view:
A test run:
A log record:
To Do
We welcome contributions! Here are some of our main priorities for continued development:
Add a –repeat option to the log_urls command so that the urls can be run through multiple times.
Write more complex performance tests that use TestCase classes and log each request from the Django test client.
Graph the aggregated stats of the runs.
Take more inspiration from Sentry and group hits on the same urls within the same run together, showing aggregated and individual stats.
1 maintainer
Metadata
1 maintainer
Release files for django-debug-logging 0.4
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 | |
|---|---|---|---|---|
| django-debug-logging-0.4.tar.gz | 55.3 kB | Without provenance | Details |
Release files / django-debug-logging-0.4.tar.gz
| Download URL | django-debug-logging-0.4.tar.gz |
|---|---|
| Size | 55.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
decd75f8a861a2767da0482ff3e0feb328afb3bf72029be24cb48d7550e336b5
|
|
BLAKE2b-256 checksum How to use checksums |
b0e06f147ba1956af649f824e92c368ea389b30543edff3276980e9f72b1194e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-debug-logging 0.4
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.
