Xray
hourly rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 24 hours▾
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:25:35.
› →|
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 30 endpoints

Endpoint-level X-ray over the last 24h — 365 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
below objective
98.00% derived · 0.0× burn
p95 vs normal
—
no baseline yet
last deploy
2d ago
[email protected] · 6db9855a
Neo4j footprint
6k
16.4 per request · 241 slow
owner · on-call
Madhava Mukkamala
backup Shashank Agrawal · CODEOWNERS /execsvc/
Endpoint Calls ▾ Avg latency Max Err %
POST /api/trialexec/v2/study/:id/activity/status 82 876 ms 10.72 s 0.0%
POST /api/trialexec/v2/study/:id/activity/details 53 232 ms 2.09 s 0.0%
GET /api/trialexec/study/:id/subject/details 26 318 ms 2.72 s 0.0%
GET /api/trialexec/careplan/:id 19 81 ms 198 ms 0.0%
GET /api/trialexec/study/:id/protocol 19 106 ms 457 ms 0.0%
POST /api/trialexec/v2/careplan/:id/activity/save 19 391 ms 819 ms 47.4%
POST /api/trialexec/v2/study/:id/activity/references 18 471 ms 6.01 s 0.0%
GET /api/trialexec/v2/careplan/:id/participantvisit/:id/activity 13 463 ms 2.34 s 0.0%
GET /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/status 13 38 ms 106 ms 0.0%
GET /api/trialexec/study/:id/site 9 69 ms 174 ms 66.7%
GET /api/trialexec/study/:id/actor 7 463 ms 2.67 s 14.3%
GET /api/trialexec/study/:id/subject 7 2.02 s 4.67 s 0.0%
GET /api/trialexec/study/:id/subject/freeze 7 142 ms 385 ms 0.0%
GET /api/trialexec/study/:id/subject/lock 7 151 ms 390 ms 0.0%
GET /api/trialexec/v2/careplan/:id/participantvisit/:id/status 7 107 ms 157 ms 0.0%
GET /api/trialexec/monitorqueries/study/:id/filter 6 838 ms 2.19 s 0.0%
GET /api/trialexec/study/:id/edcsourceoptions 6 37 ms 87 ms 0.0%
POST /api/trialexec/monitorqueries/study/:id/list 6 396 ms 698 ms 0.0%
POST /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/save 6 138 ms 595 ms 0.0%
GET /api/trialexec/v2/careplan/:id/studyprotocol 5 547 ms 1.09 s 0.0%
GET /api/trialexec/careplan/:id/visit/all 4 34 ms 46 ms 0.0%
GET /api/trialexec/v2/task/:id 4 574 ms 1.99 s 0.0%
POST /api/trialexec/v2/careplan/:id/activity/table 4 1.07 s 1.79 s 0.0%
GET /api/trialexec/monitorqueries/study/:id/groupQueriesByVisitAndSubject 3 550 ms 784 ms 0.0%
GET /api/trialexec/v2/study/:id/protocol/:id/crf 3 171 ms 184 ms 33.3%
GET /api/trialexec/v2/study/:id/subject/:id/status 3 12.01 s 16.11 s 0.0%
POST /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/edit/complete 3 328 ms 704 ms 0.0%
POST /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/edit/start 3 529 ms 1.22 s 0.0%
GET /api/trialexec/study/:id/activity 2 38 ms 45 ms 0.0%
GET /api/trialexec/study/:id/dutyplan 1 38 ms 38 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.