Design mechanism for logging query string parameters in request logs

[plittlewood-rpt]

Background context The request logs that AWS Gateway provide do not provide the granular level of detail around query string parameters, which means we don't have the full picture about what filters developers are applying to their requests. From an observability perspective we need to improve this, but having this information would also allow us to better target performance improvements based on the query string parameters that are most commonly used

Specification

• This is a research and design exercise. Familiarise yourself with the existing logging mechanism and look to improve on this. If we need to build our own logging, map out an appropriate route to do this. At the last check logging of query string parameters was not supported by AWS but this may have changed.
• Output of the ticket is fairly open and can include POC, design discussions etc, with ultimate aim of logging implementation tickets. Cloudfront may be an option here
• We should be able to do this with the multi broker now we've got everything going through it

[HollyJoyPhillips]

Internal reference: PBI-5700