Xray
hourly 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-20 19:15:22.
› →|
updated 2d 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

onboardingsvc 30 endpoints

Endpoint-level X-ray over the last 3d — 1,380 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 onboardingsvc
last deploy
—
no ArgoCD sync recorded
Neo4j footprint
5k
2.5 per request · 29 slow
owner · on-call
Prasad Limaye
backup Sambasiva Bandarupalli · CODEOWNERS /auth*/
Endpoint Calls ▴ Avg latency Max Err %
DELETE /api/organizations/deleteOrganization1/studies/:id/archive 1 281 ms 281 ms 0.0%
GET /api/organizations/SmoDeleteOrganization1/member-labels 1 35 ms 35 ms 0.0%
GET /api/organizations/SmoDeleteOrganization1/members/output 1 52 ms 52 ms 0.0%
GET /api/organizations/SmoDeleteOrganization1/studies/archived 1 26 ms 26 ms 0.0%
GET /api/organizations/cro 1 47 ms 47 ms 0.0%
GET /api/organizations/tildaScale/member-labels 1 32 ms 32 ms 0.0%
POST /api/organizations/deleteOrganization1/studies/:id/restore 1 142 ms 142 ms 0.0%
GET /api/organizations/tildaScale/members/output 2 206 ms 342 ms 0.0%
GET /api/organizations/tildaScale 3 41 ms 60 ms 0.0%
GET /api/organizations/deleteOrganization1/studies/:id/purge 4 80 ms 124 ms 0.0%
GET /api/organizations/SmoDeleteOrganization1 5 77 ms 148 ms 0.0%
GET /api/partners 6 105 ms 296 ms 0.0%
GET /api/partners/study/:id 6 86 ms 201 ms 0.0%
GET /api/roles 6 37 ms 88 ms 0.0%
GET /api/organizations/deleteOrganization1 7 61 ms 129 ms 0.0%
GET /api/organizations/deleteOrganization1/studies/archived 8 75 ms 135 ms 25.0%
GET /api/sites 8 264 ms 1.12 s 0.0%
GET /api/myprofile 10 85 ms 153 ms 0.0%
POST /register/discover-method 11 1 ms 9 ms 0.0%
GET /api/organizations/tildainc 14 53 ms 235 ms 0.0%
GET /config/oidc-config.json 21 2 ms 8 ms 0.0%
PUT /api/userprefs 87 37 ms 70 ms 0.0%
GET /api/organizations/aiTmf 125 41 ms 241 ms 0.0%
GET /api/myprofile/signature 139 26 ms 107 ms 0.0%
GET /api/myprofile/visibility/v2/study/:id 143 133 ms 734 ms 0.0%
GET /api/onboardingsvc/version 144 <1 ms 1 ms 0.0%
GET /api/myprofile/v2 150 39 ms 277 ms 0.0%
POST /api/myprofile/stillActive 156 28 ms 169 ms 0.0%
GET /api/myprofile/visibility/v2 159 39 ms 191 ms 0.0%
GET /api/userprefs 159 39 ms 198 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.