Request/Response bodies
By default, DRF API LOGGER will save down the request and response bodies for each request for future viewing no matter how large. If DRF API LOGGER is used in production under heavy volume with large bodies this can have a huge impact on space/time performance.
This behaviour can be configured with the following options additional:
DRF_API_LOGGER_MAX_REQUEST_BODY_SIZE = -1 # DRF API LOGGER takes anything <0 as no limit
DRF_API_LOGGER_MAX_RESPONSE_BODY_SIZE = 1024 # If response body>1024 bytes, ignore. Instead of an response, write, for example, "..."
Request/Response bodies By default, DRF API LOGGER will save down the request and response bodies for each request for future viewing no matter how large. If DRF API LOGGER is used in production under heavy volume with large bodies this can have a huge impact on space/time performance.
This behaviour can be configured with the following options additional:
DRF_API_LOGGER_MAX_REQUEST_BODY_SIZE = -1 # DRF API LOGGER takes anything <0 as no limit DRF_API_LOGGER_MAX_RESPONSE_BODY_SIZE = 1024 # If response body>1024 bytes, ignore. Instead of an response, write, for example, "..."