← all services
patientsvc 4 endpoints
Endpoint-level X-ray over the last 5d — 8 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
Neo4j footprint
51
5.6 per request · 6 slow
owner · on-call
Suresh Boddapati
backup Sambasiva Bandarupalli · CODEOWNERS /patientsvc/
| Endpoint | Calls ▾ | Avg latency | Max | Err % |
|---|---|---|---|---|
| GET /api/patients/:id/profile | 5 | 713 ms | 1.42 s | 40.0% |
| GET /api/patientPhis | 1 | 309 ms | 309 ms | 0.0% |
| GET /api/patients/:id/medicalConditions | 1 | 59 ms | 59 ms | 0.0% |
| GET /api/patients/:id/medications | 1 | 106 ms | 106 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.