← all services
tusker 6 endpoints
Endpoint-level X-ray over the last 14d — 70 API calls.
Endpoints are derived from the request logs and templatized (:id).
Click one for its Neo4j fan-out, traces, and logs (fetched live).
See the raw calls:
all API calls ·
failing (5xx) →
What it costs:
its bill · namespace tilda · requests vs use · its LLM calls · AI spend by org
error budget
healthy
99.90% derived · 0.0× burn
p95 vs normal
—
no baseline yet
open findings
0
nothing open for tusker
last deploy
5d ago
automated ·
5beaa388Neo4j footprint
7k
2.1 per request · 65 slow
owner · on-call
Ojas Kale
backup Taylor Futral · CODEOWNERS /tusker/
| Endpoint | Calls ▴ | Avg latency | Max | Err % |
|---|---|---|---|---|
| GET /api/inboxes/ | 1 | 1.72 s | 1.72 s | 0.0% |
| GET /api/taskfilters/ | 2 | 1.24 s | 2.26 s | 0.0% |
| GET /api/tasks/ | 3 | 1.70 s | 2.79 s | 0.0% |
| GET /api/tasks/:id/changelogs | 4 | 145 ms | 306 ms | 0.0% |
| GET /api/inboxes/user | 24 | 57 ms | 112 ms | 4.2% |
| GET /api/tasks/home/ | 36 | 129 ms | 2.00 s | 5.6% |
Per-endpoint Neo4j fan-out (and N+1 detection) is one click away on each endpoint's Queries tab — fetched live by sampling that endpoint's recent traces.