logging UI requests

The overall journey (for me) is that we receive a user bug report, jump into the API Edge Logs view, look for the request that is failing (verify based on auth_user and status of the response). Next, to figure out WHY it is failing, I go into the Postgres Logs table, and attempt to identify the related logs (sometimes unsuccessfully). Request 1: allow the API Edge Logs to be filtered by auth_user ID. Would be a quick and easy win! Request 2 [highest pri]: Connect the edge-logs to the postgres-logs. Ideally: a clickable "request_id" or other field in the edge-logs that navigates directly to the associated postgres-logs for the request in question. My understanding is that this might be feasible by the work done [here]( But I'm not totally certain on that front. Alternatively: Jump to a specific date/time more easily! Would at least help the filtering process. This could be just pasting in a timestamptz from a different logs table, and adding a ~100ms buffer (or s…