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-21 03:09:11.
› →|
updated 2d 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 5d — 11,596 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
132k
3.3 per request · 936 slow
owner · on-call
Sambasiva Bandarupalli
backup Ahmed Aburaed · CODEOWNERS /data-science/
Endpoint Calls ▾ Avg latency Max Err %
GET /api/v2/va/work-order-configs 3,417 253 ms 7.44 s 0.0%
GET /api/v1/va/work-orders/:id 3,284 113 ms 4.41 s 0.0%
GET /api/v2/va/work-order-configs/:id 794 244 ms 2.64 s 0.0%
GET /api/v1/va/work-orders/:id/wo-activities/recent 668 227 ms 4.69 s 0.0%
GET /api/v1/va/work-orders/:id/wo-tasks 451 193 ms 5.34 s 0.0%
POST /api/v1/va/sse/register 431 120 ms 4.65 s 0.7%
GET /api/v1/va/sse/stream 401 — — 0.0%
POST /api/v2/va/agents/work-order-config/run 293 9.99 s 42.83 s 2.0%
GET /api/v1/va/work-order-templates 279 175 ms 4.18 s 0.7%
GET /api/v1/va/work-orders/:id/wo-activities 164 146 ms 4.76 s 0.0%
POST /api/v2/va/work-order-configs 140 468 ms 8.34 s 0.0%
POST /api/v1/va/identify-doctype/classify-document-id 123 10 ms 117 ms 100.0%
GET /api/v1/va/work-orders/:id/documents 119 132 ms 920 ms 0.0%
GET /api/v1/va/file-upload-emails 105 209 ms 1.01 s 0.0%
PUT /api/v1/va/work-orders/wo-activities/:id 88 1.70 s 12.93 s 0.0%
POST /api/v1/va/mailgun/ai 82 2.18 s 12.12 s 0.0%
GET /api/v1/va/work-orders/wo-tasks/:id/subtasks 75 133 ms 1.26 s 0.0%
POST /api/v2/va/work-order-configs/translate-email 73 5.49 s 16.64 s 8.2%
PUT /api/v1/va/work-orders/:id 64 3.78 s 2.2 min 23.4%
DELETE /api/v1/va/sse/register 63 60 ms 816 ms 0.0%
GET /api/v1/va/work-order-templates/entity-types 59 30 ms 79 ms 0.0%
POST /api/v1/va/work-orders/:id/wo-activities 58 148 ms 855 ms 0.0%
PUT /api/v1/va/work-orders/wo-tasks/:id 41 505 ms 1.59 s 31.7%
GET /api/v1/va/work-orders/:id/changelogs 36 122 ms 270 ms 0.0%
GET /api/v1/va/work-order-emails 32 506 ms 1.09 s 9.4%
PUT /api/v2/va/work-order-configs/:id 25 194 ms 809 ms 0.0%
GET /api/v1/va/edl/events/:id/plan 22 523 ms 1.95 s 4.5%
GET /api/v1/va/file-upload-emails/filter-values 21 321 ms 1.01 s 0.0%
GET /api/v1/va/work-orders/:id/changelogs/export 18 100 ms 229 ms 0.0%
POST /api/v1/va/work-orders/wo-tasks/:id/discard 18 486 ms 1.84 s 50.0%
POST /api/v1/va/work-order-templates 16 125 ms 365 ms 0.0%
GET /api/v1/va/work-order-configs/:id 12 170 ms 421 ms 0.0%
GET /api/v1/va/skills 11 121 ms 354 ms 0.0%
POST /api/v1/va/mailgun/inbound 11 428 ms 770 ms 0.0%
POST /api/v2/va/work-order-configs/:id/recipients 11 291 ms 475 ms 0.0%
GET /api/v1/va/proxy/image 9 38 ms 162 ms 88.9%
POST /api/v1/va/work-orders/wo-tasks/:id/reactivate 9 691 ms 1.00 s 0.0%
GET /api/v1/va/work-order-emails/:id 8 575 ms 1.68 s 25.0%
POST /api/v2/va/work-order-configs/event-scope-recipients 8 1.88 s 6.01 s 0.0%
GET /api/v1/va/work-orders/wo-activities/:id 7 135 ms 262 ms 0.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/mailgun/permanent-failure 5 295 ms 1.43 s 40.0%
DELETE /api/v1/va/work-order-configs/:id 4 2.02 s 2.36 s 0.0%
GET /api/v1/va/edl/events/:id/plan/history 4 95 ms 137 ms 25.0%
GET /api/v1/va/sse/register 4 36 ms 45 ms 0.0%
POST /api/v1/va/mailgun/bounce 4 76 ms 272 ms 50.0%
POST /api/v1/va/work-order-configs/:id/send-drafts 4 — — 0.0%
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%
POST /api/v1/va/mailgun/eml 3 324 ms 954 ms 66.7%
POST /api/v1/va/work-orders/:id/documents/:id/resolve 3 1.98 s 2.88 s 0.0%
POST /api/v2/va/work-order-configs/:id/transition 3 183 ms 267 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.