Closed binarylogic closed 5 years ago
Closing this as this is already included in the controller_called
event within the :timber_phoenix
library. If users are using a framework, such as Phoenix, then parameters should be logged downstream when the request is processed. This is necessary since both the query string and body both need to be decoded and merged. Here's an example around how we do this in :timber_phoenix
:
The Timber
Plug
integration logs ahttp_request_received
event that contains data about the incoming request. By default, it does not include the parsed parameters because this data can vary greatly in size. There are scenarios where this data can be very large, but in most cases, it's not that large and can be incredibly helpful to customers. I'd like to make a few changes to this:1
above. For example, the values for this option could betrue
,false
, or{:limit, byte_size}
. Where the last option would only include the params if the byte size was <= the providedbyte_size
.I'm open to other ideas here, but incoming request parameters are incredibly valuable and it's a common support question.