← all services
schedsvc 6 endpoints
Endpoint-level X-ray over the last 48h — 75 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
1d ago
automated ·
e4eb245dNeo4j footprint
808
8.6 per request · 40 slow
owner · on-call
Murali Krishna Velamati
backup Sambasiva Bandarupalli · CODEOWNERS /schedsvc/
| Endpoint | Calls ▾ | Avg latency | Max | Err % |
|---|---|---|---|---|
| GET /api/v1/sched/CalendarPrefFilter | 27 | 203 ms | 584 ms | 3.7% |
| POST /api/v1/sched/Calender | 27 | 439 ms | 2.91 s | 3.7% |
| POST /api/v1/sched/SubjectVisitAppointments | 16 | 262 ms | 1.05 s | 0.0% |
| POST /api/v1/sched/GenerateScheduleWindow | 2 | 224 ms | 248 ms | 0.0% |
| POST /api/v1/sched/VisitAppointments | 2 | 1.08 s | 1.10 s | 0.0% |
| GET /api/v1/sched/Visit/:id/CarePlan/:id/SchedRoleInfo | 1 | 93 ms | 93 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.