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:19:38.
› →|
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

patientsvc 7 endpoints

Endpoint-level X-ray over the last 3d — 245 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 patientsvc
last deploy
1d ago
automated · e4eb245d
Neo4j footprint
669
2.4 per request · 57 slow
owner · on-call
Suresh Boddapati
backup Sambasiva Bandarupalli · CODEOWNERS /patientsvc/
Endpoint Calls ▴ Avg latency Max Err %
GET /api/patients/:id/profile 6 928 ms 1.76 s 33.3%
PATCH /api/leads/:id 8 227 ms 396 ms 0.0%
POST /api/leads 9 553 ms 2.55 s 0.0%
POST /api/patients 9 692 ms 1.50 s 0.0%
GET /api/leads/:id 17 421 ms 1.77 s 0.0%
GET /api/leads/statusHistory/:id 17 62 ms 141 ms 0.0%
GET /api/patientPhis 179 539 ms 2.84 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.