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 18:51:04.
› →|
updated 1d 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

virtual-assistant 29 endpoints

Endpoint-level X-ray over the last 3d — 1,333 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
100k
8.5 per request · 1306 slow
owner · on-call
Sambasiva Bandarupalli
backup Ahmed Aburaed · CODEOWNERS /data-science/
Endpoint Calls ▾ Avg latency Max Err %
GET /api/v1/va/work-orders/:id/wo-activities 270 231 ms 4.99 s 0.0%
GET /api/v1/va/work-orders/:id 191 151 ms 3.52 s 0.0%
GET /api/v1/va/work-orders/:id/wo-activities/recent 144 230 ms 3.95 s 0.0%
GET /api/v1/va/sse/stream 93 — — 0.0%
POST /api/v1/va/sse/register 91 52 ms 1.19 s 0.0%
GET /api/v2/va/work-order-configs 79 824 ms 7.72 s 0.0%
GET /api/v1/va/work-orders/:id/wo-tasks 72 328 ms 795 ms 0.0%
GET /api/v1/va/work-order-emails/:id 64 344 ms 1.36 s 0.0%
GET /api/v1/va/work-orders/wo-activities/:id 56 214 ms 4.20 s 0.0%
GET /api/v2/va/work-order-configs/:id 49 225 ms 1.04 s 0.0%
DELETE /api/v1/va/sse/register 48 40 ms 103 ms 0.0%
POST /api/v1/va/mailgun/ai 32 1.39 s 2.71 s 0.0%
GET /api/v1/va/work-order-templates 24 67 ms 120 ms 0.0%
POST /api/v2/va/agents/work-order-config/run 24 5.99 s 15.21 s 0.0%
POST /api/v2/va/work-order-configs/event-scope-recipients 19 328 ms 4.36 s 0.0%
POST /api/v2/va/work-order-configs/:id/recipients 13 297 ms 455 ms 0.0%
PUT /api/v1/va/work-orders/wo-activities/:id 12 294 ms 359 ms 0.0%
GET /api/v1/va/skills 11 63 ms 160 ms 0.0%
GET /api/v1/va/work-orders 6 254 ms 963 ms 0.0%
GET /api/v1/va/work-order-templates/entity-types 5 31 ms 42 ms 0.0%
GET /api/v1/va/work-orders/:id/documents 5 134 ms 467 ms 0.0%
POST /api/v1/va/steer/check 5 196 ms 347 ms 0.0%
GET /api/v1/va/edl/events/:id/plan 4 1.67 s 4.17 s 0.0%
POST /api/v1/va/steer 4 2.22 s 4.95 s 0.0%
POST /api/v2/va/work-order-configs 4 374 ms 486 ms 0.0%
POST /api/v2/va/work-order-configs/:id/send-drafts 3 — — 33.3%
PATCH /api/v1/va/steer/:id/reported 2 86 ms 105 ms 0.0%
POST /api/v1/va/steer/:id/approve 2 3.48 s 6.01 s 0.0%
POST /api/v1/va/work-orders/:id/placeholders 1 1.07 s 1.07 s 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.