Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 3 days▾
Ends now. Anything up to this cluster's 30-day retention.
Start and end times
Cancel
Interpreted in UTC (change it at the right of this bar). Earliest available: 2026-10-19 17:02:30.
› →|
updated 1d ago
Sample data. This database was generated by scripts/seed_dev_db.py — every service, deploy, person and figure on this page is synthetic. Names are sample.*@seed.invalid and image tags are prefixed SEED-. Nothing here happened.
← all services

studiosvc 38 endpoints

Endpoint-level X-ray over the last 3d — 15,871 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
last deploy
—
no ArgoCD sync recorded
Neo4j footprint
25k
1.6 per request · 378 slow
owner · on-call
Suresh Boddapati
backup Madhava Mukkamala · CODEOWNERS /studiosvc/
Endpoint Calls ▾ Avg latency Max Err %
GET /api/studio/events 15,143 21 ms 4.04 s 100.0%
GET /api/studio/forms/:id 147 2.26 s 8.70 s 0.0%
GET /api/studio/protocols/:id/deleteLocks 100 317 ms 2.21 s 0.0%
GET /api/studio/activities/:id 95 1.23 s 7.59 s 0.0%
GET /api/studio/forms/:id/summary 76 89 ms 2.60 s 0.0%
GET /api/studio/protocols/:id/visits/:id 55 787 ms 3.30 s 7.3%
GET /api/studio/tables/:id 45 2.36 s 6.59 s 0.0%
GET /api/studio/forms 33 837 ms 5.71 s 0.0%
GET /api/studio/allowedObjList 27 15 ms 35 ms 0.0%
GET /api/studio/activities 25 860 ms 2.83 s 0.0%
POST /api/studio/graph/:id/nodeAction 21 751 ms 4.56 s 4.8%
GET /api/studio/protocols/:id/objectCounts 18 68 ms 203 ms 0.0%
GET /api/studio/questions/:id 12 167 ms 492 ms 0.0%
GET /api/studio/activities/:id/summary 9 33 ms 55 ms 0.0%
GET /api/studio/dataMapping/objTypes 8 14 ms 19 ms 0.0%
GET /api/studio/functions 7 34 ms 90 ms 0.0%
PATCH /api/studio/forms/:id 7 3.88 s 13.00 s 0.0%
GET /api/studio/questions 6 326 ms 854 ms 0.0%
GET /api/studio/responseSets 4 1.58 s 6.06 s 0.0%
GET /api/studio/forms/:id/activationRuleChains 3 154 ms 350 ms 0.0%
GET /api/studio/tables/:id/summary 3 42 ms 49 ms 0.0%
POST /api/studio/activities 3 489 ms 968 ms 0.0%
POST /api/studio/forms 3 229 ms 327 ms 0.0%
GET /api/studio/dataMapping/objTypes/CarePlan/dataNames 2 8 ms 9 ms 0.0%
GET /api/studio/tables 2 963 ms 996 ms 0.0%
PATCH /api/studio/tables/:id 2 124 ms 188 ms 0.0%
POST /api/studio/forms/:id/activationRuleChains 2 64 ms 65 ms 0.0%
POST /api/studio/forms/:id/activationRules 2 108 ms 121 ms 0.0%
POST /api/studio/tables 2 188 ms 286 ms 0.0%
DELETE /api/studio/forms/:id 1 11.30 s 11.30 s 0.0%
GET /api/studio/dataMapping/objTypes/Phi/dataNames 1 9 ms 9 ms 0.0%
GET /api/studio/dataMapping/objTypes/Study/dataNames 1 9 ms 9 ms 0.0%
GET /api/studio/protocols/:id/autoqueries 1 375 ms 375 ms 0.0%
GET /api/studio/responseSets/:id 1 106 ms 106 ms 0.0%
GET /api/studio/workflows 1 209 ms 209 ms 0.0%
PATCH /api/studio/activities/:id 1 160 ms 160 ms 0.0%
POST /api/studio/questions 1 93 ms 93 ms 0.0%
PUT /api/studio/questions/:id 1 1.71 s 1.71 s 0.0%

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.