Browse request and Function execution logs for a project — 'was it my engine or my Function code' debugging, with rich filtering.
log_type='requests' returns one row per API request (status, latency split into engine vs. Function time, redacted payload). log_type='function_logs' returns one row per Function invocation within a request's chain (status, duration, its own error text in full, and its captured print() output). The two share a requestId — use get_request_trace to fetch both sides of one request in a single call.
Filters: tenant_id, entity, http_method, and (function_logs only) function_id are exact-match and fast. At least one of those, an exact request_id, or a bounded created_after/created_before time range is required — an unfiltered, unbounded query is rejected, since `requests` rows never expire.