← all services
schedsvc 4 endpoints
Endpoint-level X-ray over the last 48h — 18 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
—
no ArgoCD sync recorded
Neo4j footprint
587
23.8 per request · 14 slow
owner · on-call
Murali Krishna Velamati
backup Sambasiva Bandarupalli · CODEOWNERS /schedsvc/
| Endpoint | Calls ▾ | Avg latency | Max | Err % |
|---|---|---|---|---|
| GET /api/v1/sched/CalendarPrefFilter | 7 | 174 ms | 305 ms | 0.0% |
| POST /api/v1/sched/Calender | 7 | 297 ms | 464 ms | 0.0% |
| POST /api/v1/sched/SubjectVisitAppointments | 3 | 218 ms | 328 ms | 0.0% |
| POST /api/v1/sched/GenerateSchedules | 1 | 655 ms | 655 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.