This package provides middleware for automatically logging exceptions in Django applications. It captures and stores exception details such as the error message, stack trace, request data, headers, and the view where the error occurred.
- Automatically logs exceptions in the database
- Captures request payloads and headers for debugging
- Customizable via model relationships with your user model
- Handles specific exceptions like
PermissionDeniedandParseErrorwith customized responses
- Python 3.8+
- Django 3.2+
- Django Rest Framework 3.12+
-
Install the package
You can install this package from PyPI using pip:
pip install django-rest-exception-logger
-
Add the middleware
To enable automatic exception logging, add
ExceptionMiddlewareto yourMIDDLEWARElist in your Django project'ssettings.pyfile:MIDDLEWARE = [ # Other middlewares... 'django_rest_exception_logger.middleware.ExceptionMiddleware', ]
-
Add the ExceptionLog model
This package comes with the
ExceptionLogmodel, which stores information about exceptions. You need to integrate it into your project.-
Add
exception_loggingto theINSTALLED_APPSlist insettings.py:INSTALLED_APPS = [ # Other apps... 'django_rest_exception_logger', ]
-
Run migrations to create the necessary database tables:
python manage.py migrate
-
if migration not detected, run this command
python manage.py makemigrations django_rest_exception_logger
-
-
Configure the user model (optional)
By default, the
ExceptionLogmodel has a foreign key to theauth.Usermodel. If you are using a custom user model, ensure that theExceptionLogmodel'suserfield is compatible with your custom user model. -
Customize Middleware behavior (optional)
You can extend the
ExceptionMiddlewareor modify it to add additional custom exception handling as needed for your application.
Once the middleware is installed, it will automatically log exceptions that occur in your views to the ExceptionLog model. The logged information will include:
- Exception type and message
- Full traceback
- Request payload (for POST, PUT, PATCH requests)
- Request headers and parameters
- View name where the exception occurred
- User who initiated the request (if available)
If you need to log exceptions from other places (views, Celery tasks, management
commands, signals), you can use log_exception.
from django_rest_exception_logger.utils import log_exception
try:
# ... your code ...
raise ValueError("Invalid input")
except Exception as exc:
log_exception(
exc,
request=request, # optional
message="Payment failed", # optional override for ExceptionLog.message
extra={"order_id": 123, "step": "charge"}, # optional extra context
log_type="error", # optional (default: "error")
view_name="payments.charge", # optional override
)extra is stored under "_extra" inside request_payload.
# 1. Query All Error Logs
from django_rest_exception_logger.models import ExceptionLog
# Retrieve all error logs ordered by most recent
error_logs = ExceptionLog.objects.filter(log_type="error").order_by('-timestamp')
for log in error_logs:
print(log.message, log.timestamp)
# 2. Create a New Info Log
from django_rest_exception_logger.models import ExceptionLog
# Create a new info log entry
ExceptionLog.objects.create(
log_type="info",
message="This is an informational log",
view_name="my_view"
)- Debugging Production Issues: Track unexpected errors in production environments with full context, including which user triggered the error and what data they sent.
- Security Auditing: Capture unauthorized access attempts and permission errors for analysis and potential remediation.
- Improving User Experience: With detailed logs, identify common errors and enhance your application's stability and error handling.
Run the test suite:
pip install -r requirements-dev.txt # if you use a dev requirements file
pytestTo manually verify middleware behavior, you can raise an exception in a view and check the logs in your admin or database:
def test_view(request):
raise Exception("Test exception for logging")After visiting this view, a new entry should appear in the ExceptionLog model, capturing the details of the error.
Feel free to open an issue or submit a pull request if you have suggestions for improvements.
This project is licensed under the MIT License - see the LICENSE file for details.