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 12:01:20.
› →|
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 — 184 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
779
3.9 per request · 47 slow
owner · on-call
Suresh Boddapati
backup Sambasiva Bandarupalli · CODEOWNERS /patientsvc/
Endpoint Calls ▴ Avg latency Max Err %
PATCH /api/leads/:id 3 270 ms 376 ms 0.0%
POST /api/leads 3 425 ms 876 ms 0.0%
POST /api/patients 3 1.03 s 1.85 s 0.0%
GET /api/leads/:id 6 659 ms 1.76 s 0.0%
GET /api/leads/statusHistory/:id 6 76 ms 139 ms 0.0%
GET /api/patients/:id/profile 14 414 ms 1.45 s 35.7%
GET /api/patientPhis 149 234 ms 1.51 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.