logging UI requests

[anngbaum]

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 something like that). I'm usually not sure whether the timestamp is in my tz and whether the supabase studio client is using my tz, so it just takes a little work to get to the right time.
Previous discussion here as well.

Request 3: index query metadata for postgres-logs
This is just a lazy request because I know you can do it from the query interface, but most often when I'm looking in the postgres-logs UI, I am really trying to break down what's going on in the query. It would be great if I could just search on that directly from the interface. Additionally, it's usually some RPC that's getting called, which would be super helpful to have indexed as well.