Danger
err:user:bad_request:invalid_analytics_tableExample
What Happened?#
Your query tried to access a table that either doesn't exist or isn't allowed for security reasons.
How to Fix It#
1. Use the Correct Table Name#
2. Fix Typos in Table Names#
Available Tables#
| Endpoint | Table Name | Description |
|---|---|---|
analytics.getVerifications | key_verifications_v1 | Raw verification events |
analytics.getVerifications | key_verifications_per_minute_v1 | Minute-level aggregates |
analytics.getVerifications | key_verifications_per_hour_v1 | Hour-level aggregates |
analytics.getVerifications | key_verifications_per_day_v1 | Day-level aggregates |
analytics.getVerifications | key_verifications_per_month_v1 | Month-level aggregates |
analytics.getRatelimits | ratelimits_v1 | Raw rate limit events |
analytics.getRatelimits | ratelimits_per_minute_v1 | Minute-level aggregates |
analytics.getRatelimits | ratelimits_per_hour_v1 | Hour-level aggregates |
analytics.getRatelimits | ratelimits_per_day_v1 | Day-level aggregates |
analytics.getRatelimits | ratelimits_per_month_v1 | Month-level aggregates |
analytics.getRuntimeLogs | runtime_logs_v1 | Runtime logs of your deployments |
analytics.getGatewayRequests | gateway_requests_v1 | Raw gateway requests |