← all services
schedsvc 3 endpoints
Endpoint-level X-ray over the last 5d — 35 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 schedsvc
last deploy
4d ago
automated ·
5beaa388Neo4j footprint
581
4.9 per request · 7 slow
owner · on-call
Murali Krishna Velamati
backup Sambasiva Bandarupalli · CODEOWNERS /schedsvc/
| Endpoint | Calls ▴ | Avg latency | Max | Err % |
|---|---|---|---|---|
| POST /api/v1/sched/SubjectVisitAppointments | 9 | 160 ms | 291 ms | 11.1% |
| GET /api/v1/sched/CalendarPrefFilter | 13 | 155 ms | 456 ms | 7.7% |
| POST /api/v1/sched/Calender | 13 | 215 ms | 506 ms | 7.7% |
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.