Analytics
The Analytics page (/analytics) shows API traffic for the active
project over the last 30 days.
Views available
| View | What it shows |
|---|---|
| Uptime | Successful-call ratio over time. |
| Latency | P50 / P95 / P99 latency at the request-handler boundary. |
| Failed requests | Non-200 responses, grouped by error code. |
| Volume | Total requests over time, bucketed by hour or day. |
| Timeline | Activity stream with per-call rows. |
| By action | Volume + latency split by biofrq.detect, biofrq.identify, etc. |
| Request Journal | Per-request audit table with requestId, action, status, latency. |
Scope
- Project — every view is scoped to the project selected in the floating bar's project pill. Switch projects to re-scope the whole page.
- Window — fixed 30-day window. A date-picker is on the roadmap; until it ships, the page always shows the trailing 30 days.
Request Journal filters
The Journal table at the bottom of the page exposes a status filter chip row: All / Success / Error. Other dimensions (action, key, requestId search) are not filterable from this surface today — rely on the per-chart breakdowns above.
Cross-references with the API
Every Journal row carries the call's requestId. Copying it lets
you correlate against your application logs.
What's next
- Money Audit — the billing-side view of the same calls.
- Errors — what each failure code in the Failed-requests view means.