Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 5 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 08:23:50.
› →|
updated 21h 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

execsvc 46 endpoints

Endpoint-level X-ray over the last 5d — 1,141 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
98.00% derived · 0.0× burn
p95 vs normal
—
no baseline yet
last deploy
2d ago
[email protected] · 6db9855a
Neo4j footprint
52k
18.8 per request · 8975 slow
owner · on-call
Madhava Mukkamala
backup Shashank Agrawal · CODEOWNERS /execsvc/
Endpoint Calls ▾ Avg latency Max Err %
GET /api/trialexec/study/:id/site 107 122 ms 1.99 s 72.9%
POST /api/trialexec/v2/study/:id/activity/status 100 7.77 s 4.6 min 3.0%
GET /api/trialexec/study/:id/subject/details 89 892 ms 9.52 s 0.0%
POST /api/trialexec/v2/study/:id/activity/details 83 382 ms 8.17 s 0.0%
GET /api/trialexec/study/:id/actor 70 501 ms 3.21 s 18.6%
GET /api/trialexec/study/:id/protocol 63 214 ms 1.80 s 1.6%
GET /api/trialexec/study/:id/subject 48 7.71 s 24.39 s 0.0%
GET /api/trialexec/study/:id/edcsourceoptions 44 55 ms 358 ms 0.0%
GET /api/trialexec/study/:id/subject/freeze 44 571 ms 5.90 s 0.0%
GET /api/trialexec/study/:id/subject/lock 44 556 ms 6.00 s 0.0%
GET /api/trialexec/careplan/:id 43 360 ms 6.19 s 0.0%
POST /api/trialexec/monitorqueries/study/:id/list 42 1.95 s 11.88 s 4.8%
GET /api/trialexec/v2/careplan/:id/participantvisit/:id/activity 35 504 ms 2.98 s 0.0%
GET /api/trialexec/monitorqueries/study/:id/groupQueriesByVisitAndSubject 34 1.07 s 4.29 s 0.0%
GET /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/status 33 191 ms 3.77 s 0.0%
GET /api/trialexec/monitorqueries/study/:id/filter 31 1.36 s 6.43 s 3.2%
GET /api/trialexec/v2/careplan/:id/participantvisit/:id/status 25 714 ms 8.37 s 0.0%
POST /api/trialexec/v2/study/:id/activity/references 24 517 ms 6.01 s 0.0%
GET /api/trialexec/v2/task/:id 21 959 ms 7.62 s 0.0%
GET /api/trialexec/v2/training/mine 19 1.04 s 4.47 s 0.0%
POST /api/trialexec/v2/careplan/:id/activity/save 19 391 ms 819 ms 47.4%
GET /api/trialexec/careplan/:id/visit/all 16 115 ms 687 ms 0.0%
GET /api/trialexec/study/:id/activity 14 537 ms 1.75 s 0.0%
GET /api/trialexec/v2/careplan/:id/studyprotocol 12 953 ms 5.95 s 0.0%
GET /api/trialexec/study/:id/dutyplan 8 260 ms 1.35 s 12.5%
GET /api/trialexec/v2/study/:id/subject/:id/status 8 30.93 s 45.05 s 0.0%
POST /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/save 8 305 ms 990 ms 0.0%
POST /api/trialexec/v2/study/:id/actor 8 822 ms 2.40 s 37.5%
GET /api/trialexec/v2/study/:id/kpi 7 97 ms 286 ms 0.0%
POST /api/trialexec/monitorqueries/study/:id/count 6 3.74 s 10.85 s 16.7%
POST /api/trialexec/monitorqueries/study/:id/type 6 2.49 s 6.79 s 16.7%
GET /api/trialexec/v2/study/:id/protocol/:id/crf 4 207 ms 314 ms 25.0%
POST /api/trialexec/v2/careplan/:id/activity/table 4 1.07 s 1.79 s 0.0%
POST /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/edit/complete 4 718 ms 1.89 s 0.0%
POST /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/edit/start 4 1.18 s 3.14 s 0.0%
GET /api/trialexec/v2/study/:id/training 3 166 ms 454 ms 33.3%
PUT /api/trialexec/v2/study/:id/actor/:id 2 2.77 s 2.79 s 0.0%
GET /api/trialexec/featureflag 1 21 ms 21 ms 0.0%
GET /api/trialexec/study/:id/actor/:id/sidePanel 1 2.89 s 2.89 s 0.0%
GET /api/trialexec/v2/org/training 1 474 ms 474 ms 0.0%
POST /api/trialexec/careplan/:id/query 1 1.31 s 1.31 s 0.0%
POST /api/trialexec/careplan/:id/query/:id 1 679 ms 679 ms 0.0%
POST /api/trialexec/study/:id/protocol/:id 1 3.77 s 3.77 s 0.0%
POST /api/trialexec/study/:id/protocol/:id/adopt 1 1.05 s 1.05 s 0.0%
POST /api/trialexec/study/:id/site 1 14 ms 14 ms 100.0%
POST /api/trialexec/v2/careplan/:id/query/ 1 425 ms 425 ms 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.