Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 7 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 23:15:02.
› →|
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 53 endpoints

Endpoint-level X-ray over the last 7d — 14,650 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
149k
3.1 per request · 1215 slow
owner · on-call
Sambasiva Bandarupalli
backup Ahmed Aburaed · CODEOWNERS /data-science/
Endpoint Calls ▴ Avg latency Max Err %
GET /api/v1/va/edl/events/:id/plan/deliverables/:id/rows 3 204 ms 233 ms 33.3%
GET /api/v1/va/work-orders 3 500 ms 1.16 s 0.0%
GET /api/v1/va/edl/events/:id/plan/history 4 95 ms 137 ms 25.0%
PATCH /api/v1/va/work-orders/wo-tasks/:id/subtasks/:id 5 94 ms 172 ms 100.0%
POST /api/v1/va/edl/events/:id/plan/generate 5 2.06 s 3.55 s 40.0%
POST /api/v1/va/work-orders/:id/documents/:id/resolve 5 1.82 s 2.88 s 0.0%
POST /api/v2/va/work-order-configs/:id/transition 5 198 ms 267 ms 0.0%
GET /api/v1/va/sse/register 6 46 ms 106 ms 0.0%
POST /api/v1/va/mailgun/eml 6 340 ms 1.05 s 66.7%
DELETE /api/v1/va/work-order-configs/:id 7 2.13 s 3.71 s 0.0%
POST /api/v1/va/work-order-configs/:id/send-drafts 7 — — 0.0%
POST /api/v1/va/mailgun/bounce 8 85 ms 350 ms 50.0%
POST /api/v1/va/mailgun/permanent-failure 10 331 ms 1.80 s 40.0%
GET /api/v1/va/work-orders/wo-activities/:id 12 136 ms 262 ms 0.0%
POST /api/v1/va/work-orders/wo-tasks/:id/reactivate 12 680 ms 1.00 s 0.0%
POST /api/v2/va/work-order-configs/event-scope-recipients 12 1.89 s 6.01 s 0.0%
GET /api/v1/va/skills 13 120 ms 354 ms 0.0%
POST /api/v2/va/work-order-configs/:id/recipients 17 290 ms 475 ms 0.0%
GET /api/v1/va/proxy/image 18 35 ms 162 ms 88.9%
GET /api/v1/va/work-order-emails/:id 18 516 ms 2.23 s 22.2%
GET /api/v1/va/work-order-configs/:id 20 162 ms 421 ms 0.0%
GET /api/v1/va/work-orders/:id/changelogs/export 22 98 ms 229 ms 0.0%
POST /api/v1/va/mailgun/inbound 24 358 ms 770 ms 0.0%
POST /api/v1/va/work-order-templates 24 129 ms 431 ms 0.0%
POST /api/v1/va/work-orders/wo-tasks/:id/discard 24 476 ms 1.84 s 50.0%
GET /api/v1/va/edl/events/:id/plan 27 516 ms 1.95 s 3.7%
PUT /api/v2/va/work-order-configs/:id 41 188 ms 809 ms 0.0%
GET /api/v1/va/work-orders/:id/changelogs 44 120 ms 270 ms 0.0%
GET /api/v1/va/file-upload-emails/filter-values 48 350 ms 1.32 s 0.0%
PUT /api/v1/va/work-orders/wo-tasks/:id 48 545 ms 1.59 s 29.2%
POST /api/v1/va/work-orders/:id/wo-activities 68 146 ms 855 ms 0.0%
DELETE /api/v1/va/sse/register 69 62 ms 816 ms 0.0%
GET /api/v1/va/work-order-templates/entity-types 77 29 ms 83 ms 0.0%
GET /api/v1/va/work-order-emails 88 368 ms 1.09 s 6.8%
PUT /api/v1/va/work-orders/:id 92 3.17 s 2.2 min 22.8%
PUT /api/v1/va/work-orders/wo-activities/:id 103 1.74 s 12.93 s 0.0%
POST /api/v1/va/mailgun/ai 110 2.13 s 12.12 s 0.0%
POST /api/v2/va/work-order-configs/translate-email 114 5.04 s 16.64 s 8.8%
GET /api/v1/va/work-orders/wo-tasks/:id/subtasks 124 115 ms 1.26 s 0.0%
GET /api/v1/va/work-orders/:id/documents 144 139 ms 1.12 s 0.0%
POST /api/v1/va/identify-doctype/classify-document-id 175 10 ms 117 ms 100.0%
POST /api/v2/va/work-order-configs 202 494 ms 8.34 s 0.0%
GET /api/v1/va/file-upload-emails 210 226 ms 1.16 s 0.0%
GET /api/v1/va/work-orders/:id/wo-activities 278 148 ms 4.76 s 0.0%
GET /api/v1/va/work-order-templates 375 177 ms 4.18 s 0.5%
POST /api/v2/va/agents/work-order-config/run 403 9.57 s 42.83 s 2.5%
GET /api/v1/va/sse/stream 476 — — 0.0%
POST /api/v1/va/sse/register 522 114 ms 4.65 s 0.6%
GET /api/v1/va/work-orders/:id/wo-tasks 578 204 ms 5.34 s 0.0%
GET /api/v1/va/work-orders/:id/wo-activities/recent 765 260 ms 4.69 s 0.0%
GET /api/v2/va/work-order-configs/:id 1,068 255 ms 3.26 s 0.0%
GET /api/v1/va/work-orders/:id 3,896 113 ms 4.41 s 0.0%
GET /api/v2/va/work-order-configs 4,215 259 ms 7.47 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.