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 08:50:30.
› →|
updated 22h 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

workplansvc 18 endpoints

Endpoint-level X-ray over the last 3d — 465 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
455k
18.8 per request · 9885 slow
owner · on-call
Suresh Boddapati
backup Madhava Mukkamala · CODEOWNERS /workplansvc/
Endpoint Calls ▾ Avg latency Max Err %
GET /api/workplan/instances/:id 124 206 ms 2.03 s 0.0%
GET /api/workplan/configs/:id 101 497 ms 3.02 s 0.0%
GET /api/workplan/types/:id 98 72 ms 251 ms 0.0%
GET /api/workplan/templates/:id 13 88 ms 271 ms 0.0%
POST /api/workplan/configs 13 952 ms 3.53 s 7.7%
POST /api/workplan/templates 13 127 ms 259 ms 0.0%
POST /api/workplan/types 13 408 ms 2.94 s 0.0%
POST /api/workplan/types/:id/milestones 13 143 ms 319 ms 0.0%
POST /api/workplan/configs/:id/archive 12 165 ms 290 ms 16.7%
POST /api/workplan/configs/:id/publish 12 206 ms 363 ms 16.7%
POST /api/workplan/templates/:id/publish 12 115 ms 221 ms 0.0%
PUT /api/workplan/configs/:id/instructions 11 971 ms 2.50 s 0.0%
GET /api/workplan/configs 7 163 ms 395 ms 0.0%
GET /api/workplan/types 7 269 ms 454 ms 0.0%
GET /api/workplan/events 6 — — 0.0%
GET /api/workplan/templates 5 556 ms 939 ms 0.0%
DELETE /api/workplan/types/:id 3 43 ms 45 ms 100.0%
DELETE /api/workplan/configs/:id 2 364 ms 502 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.