Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 5 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:44:55.
› →|
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

virtual-assistant 40 endpoints

Endpoint-level X-ray over the last 5d — 2,038 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
129k
8.3 per request · 1413 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 352 206 ms 4.99 s 0.0%
GET /api/v1/va/work-orders/:id 339 122 ms 3.52 s 0.0%
GET /api/v1/va/work-orders/:id/wo-activities/recent 211 213 ms 3.95 s 0.0%
GET /api/v1/va/sse/stream 123 — — 0.0%
GET /api/v2/va/work-order-configs 123 659 ms 7.72 s 0.0%
POST /api/v1/va/sse/register 121 48 ms 1.19 s 0.0%
GET /api/v1/va/work-orders/wo-activities/:id 108 153 ms 4.20 s 0.0%
GET /api/v1/va/work-orders/:id/wo-tasks 100 255 ms 795 ms 0.0%
GET /api/v2/va/work-order-configs/:id 73 221 ms 1.55 s 0.0%
GET /api/v1/va/work-order-emails/:id 68 349 ms 1.36 s 0.0%
DELETE /api/v1/va/sse/register 65 39 ms 103 ms 0.0%
GET /api/v1/va/work-orders/:id/documents 64 145 ms 682 ms 0.0%
POST /api/v1/va/mailgun/ai 48 1.70 s 6.86 s 0.0%
GET /api/v1/va/work-order-templates 25 74 ms 239 ms 0.0%
POST /api/v2/va/agents/work-order-config/run 24 5.99 s 15.21 s 0.0%
GET /api/v1/va/work-order-configs/:id 23 127 ms 280 ms 0.0%
PUT /api/v1/va/work-orders/wo-activities/:id 22 334 ms 574 ms 0.0%
POST /api/v2/va/work-order-configs/event-scope-recipients 19 328 ms 4.36 s 0.0%
POST /api/v1/va/steer 14 3.36 s 19.82 s 0.0%
POST /api/v1/va/steer/check 13 221 ms 801 ms 0.0%
POST /api/v2/va/work-order-configs/:id/recipients 13 297 ms 455 ms 0.0%
GET /api/v1/va/skills 12 62 ms 160 ms 0.0%
GET /api/v1/va/work-orders 12 540 ms 1.15 s 0.0%
GET /api/v1/va/edl/events/:id/plan 11 1.04 s 4.17 s 0.0%
GET /api/v1/va/work-order-configs 6 228 ms 1.07 s 50.0%
GET /api/v1/va/work-order-emails 6 983 ms 1.15 s 0.0%
POST /api/v2/va/work-order-configs 6 675 ms 2.34 s 0.0%
GET /api/v1/va/file-upload-emails 5 210 ms 263 ms 0.0%
GET /api/v1/va/work-order-templates/entity-types 5 31 ms 42 ms 0.0%
PATCH /api/v1/va/steer/:id/reported 5 81 ms 105 ms 0.0%
POST /api/v1/va/steer/:id/approve 5 7.62 s 20.20 s 0.0%
GET /api/v1/va/steer/check 4 277 ms 818 ms 0.0%
GET /api/v1/va/file-upload-emails/filter-values 3 284 ms 316 ms 0.0%
POST /api/v2/va/work-order-configs/:id/send-drafts 3 — — 33.3%
POST /api/v1/va/steer/:id/reject 2 98 ms 118 ms 0.0%
GET /api/v1/va/proxy/image 1 413 ms 413 ms 0.0%
GET /api/v1/va/skills/activity 1 30 ms 30 ms 100.0%
GET /api/v1/va/work-order-configs/counts 1 192 ms 192 ms 0.0%
POST /api/v1/va/work-orders/:id/placeholders 1 1.07 s 1.07 s 0.0%
PUT /api/v2/va/work-order-configs/:id 1 169 ms 169 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.