Audience: Admin
Usage (Admin) shows a live Usage overview: popularity, abuse/security pressure, and platform activity. Panel subtitle: Popularity, abuse signals, and platform activity.
| Role | Purpose |
|---|---|
| Admin | Monitor hosted traffic, abuse signals, and builder/API activity |
Route requires Admin.
📷 Usage overview
Image Path:
images/administration-usage.png
Alt Text:
Usage page with Popularity, Abuse / security, and Platform usage sections
Caption:
Admin Usage overview.
Which published apps get traffic
Example cards and charts (when metrics exist): Hosted loads, public data volume, Top apps by hosted loads / Top apps by public data.
Floods, credential stuffing, and error pressure
Example signals: API rate, auth failure rate, rate-limit hits, error share; chart Rate limits by limiter.
LokAkrt and builder activity
Example signals: API responses, publishes, agent runs; chart API traffic by area.
Every assistant run is recorded (steps, questions, answers, and outcomes for applied and discarded runs). Workspace Usage does not show a full run timeline with prompt text. Operators review a request in the AI operator console (ui/ai, typically port 5200) — open the request list there for step-by-step detail.
Use Refresh to reload. The page may auto-refresh while open. There are no user-facing time-range filters on this screen — data is instance-wide from the metrics scrape.
Empty copy appears when no usage signals are available yet.
| Action | Access |
|---|---|
| Open Usage | Admin only |
| Problem | Cause | Solution |
|---|---|---|
| Menu item missing | Not Admin | Use an Admin account |
| Empty overview | No metrics yet / scrape restricted | Check Server status and Security metrics settings |
| Numbers look stale | Scrape lag | Click Refresh |