Drf-api-logger

Latest version: v1.1.16

Safety actively analyzes 723144 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

1.1.10

1.0.10

1. [DjangoAdmin] KeyError when trying to delete multiple API Logger entry issue fixed.
2. New feature added to log only selected methods.

1.0.9

1. API field max_length increase from 512 to 1024.
2. Add support for a list of dicts to hide sensitive data.
3. Timezone support added.

For more info, check README.md

1.0.8

You can also identify slow APIs by specifying DRF_API_LOGGER_SLOW_API_ABOVE in settings.py.

A new filter (By API Performance) will be visible, and you can choose slow or fast API.
`DRF_API_LOGGER_SLOW_API_ABOVE = 200 Default to None`
Now you can delete the DRF API Logger using the admin panel.

1.0.7

You may wish to hide sensitive information from being exposed in the logs.
You do this by setting `DRF_API_LOGGER_EXCLUDE_KEYS` in settings.py to a list of your desired sensitive keys.
The default is
`DRF_API_LOGGER_EXCLUDE_KEYS = ['password', 'token', 'access', 'refresh']`
Sensitive data will be replaced with "***FILTERED***".

You can specify the database where to store DRF API Logger logs by specifying `DRF_API_LOGGER_DEFAULT_DATABASE`.
DRF_API_LOGGER_DEFAULT_DATABASE = 'default' Default to "default" if not specified
Make sure to migrate the database specified in DRF_API_LOGGER_DEFAULT_DATABASE.

1.0.6

Logging everything issue fixed.
A new graph added to show the number of API calls by status code.

Page 2 of 4

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.