maykinmedia/django-log-outgoing-requests

Log outgoing requests made by requests library

django-log-outgoing-requests's Issues

Implement and provide default settings

So that projects don't need to provide/duplicate all the settings and we ship with sane defaults.

For example: https://github.com/jazzband/django-cookie-consent/blob/master/cookie_consent/conf.py

Add changelog

It's currently missing

Move periodic "purge records" implementation to the library

This is currently implemented in Open Forms to interface with Celery tasks, but we can avoid leaking those implementation details.

Ideally, this library offers two things:

• a function log_outgoing_requests.service.purge_log_records, taking the (optional?) argument older_than which is a number of days
• an equivalent management command purge_outgoing_request_logs, taking the --older-than CLI flag which calls the function above.

This allows users of the library to decide for themselves if they want to hook this up via a celery beat task or a cronjob like solution where the management command is called (could be cron on a VM or kubernetes cronjob, or just manual invoking for low-traffic projects).

This way we avoid pulling in all of celery as a dependency and offer maximum flexibility while still hiding our own implementation details.

Support Django 4.2

Request: Display body of request

(i'll skip the part about security/privacy)
Just the outgoing request doesn't tell the whole story, especially in a system where requests to a single end-point accepts all kinds of request like a ESB.
These endpoints can respond with a 200, but in fact return a exception in the body.

Wishes for this feature:

• Enable body logging for x minutes
• Purge body logs after x time
• Style body syntax
• Show a "copy" button
• Show a "delete" button