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 07:52:05.
› →|
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 29 endpoints

Endpoint-level X-ray over the last 24h — 187 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
1k
5.9 per request · 61 slow
owner · on-call
Madhava Mukkamala
backup Shashank Agrawal · CODEOWNERS /execsvc/
Endpoint Calls ▾ Avg latency Max Err %
GET /api/trialexec/study/:id/actor 15 367 ms 1.02 s 40.0%
GET /api/trialexec/study/:id/subject/details 14 375 ms 1.19 s 0.0%
POST /api/trialexec/v2/study/:id/activity/details 12 362 ms 1.78 s 0.0%
GET /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/status 11 152 ms 788 ms 0.0%
GET /api/trialexec/study/:id/subject 10 331 ms 808 ms 0.0%
GET /api/trialexec/study/:id/subject/freeze 10 280 ms 803 ms 0.0%
GET /api/trialexec/study/:id/subject/lock 10 298 ms 905 ms 0.0%
POST /api/trialexec/v2/study/:id/activity/status 10 217 ms 1.20 s 0.0%
GET /api/trialexec/study/:id/edcsourceoptions 9 247 ms 689 ms 0.0%
GET /api/trialexec/study/:id/protocol 9 303 ms 1.27 s 0.0%
GET /api/trialexec/study/:id/site 9 401 ms 1.01 s 0.0%
GET /api/trialexec/monitorqueries/study/:id/groupQueriesByVisitAndSubject 8 489 ms 1.20 s 0.0%
GET /api/trialexec/v2/careplan/:id/participantvisit/:id/activity 7 399 ms 1.59 s 0.0%
GET /api/trialexec/v2/careplan/:id/participantvisit/:id/status 7 574 ms 1.20 s 0.0%
GET /api/trialexec/careplan/:id 6 1.61 s 2.41 s 0.0%
GET /api/trialexec/study/:id/activity 6 169 ms 246 ms 0.0%
GET /api/trialexec/v2/careplan/:id/studyprotocol 6 275 ms 1.01 s 0.0%
POST /api/trialexec/v2/study/:id/activity/references 6 423 ms 2.35 s 0.0%
POST /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/save 4 327 ms 632 ms 0.0%
GET /api/trialexec/study/:id/dutyplan 3 162 ms 211 ms 0.0%
GET /api/trialexec/study/:id/staffLabels 3 42 ms 60 ms 0.0%
GET /api/trialexec/v2/study/:id/subject/:id/status 2 696 ms 1.13 s 0.0%
GET /api/trialexec/v2/training/mine 2 282 ms 288 ms 0.0%
POST /api/trialexec/v2/careplan/:id/auditlogs/ 2 112 ms 206 ms 0.0%
POST /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/edit/start 2 922 ms 1.67 s 0.0%
POST /api/trialexec/careplan/:id/visit/:id/start 1 169 ms 169 ms 0.0%
POST /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/complete 1 519 ms 519 ms 0.0%
POST /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/edit/abort 1 460 ms 460 ms 0.0%
POST /api/trialexec/v2/careplan/:id/participantvisit/:id/activity/edit/complete 1 1.31 s 1.31 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.