Grep the function logs without leaving HTTP

Four hundred webhook deliveries ran this morning; one threw. The exec logs API answers on the same hostname as the scripts: list every log file, stream them live, read paginated slices, or run a regex search across everything the executions wrote. orderId.*4417 finds the failing delivery in one request. When the incident closes, prune the old entries with another.

The usual arrangement is different: functions run in one place and log into another: a separate observability product with its own query language you relearn every incident.

Here stdout sits one URL away from the code that produced it.

The logs live where the function lives.