Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 14 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 10:35:19.
› →|
updated 23h 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 45 endpoints

Endpoint-level X-ray over the last 14d — 3,080 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
1d ago
automated · 40d07ba1
Neo4j footprint
47k
3.5 per request · 555 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 834 131 ms 4.69 s 0.5%
GET /api/v2/va/work-order-configs 541 591 ms 5.70 s 0.2%
GET /api/v1/va/work-orders/:id/wo-activities/recent 266 369 ms 6.24 s 2.3%
GET /api/v1/va/sse/stream 248 — — 0.0%
POST /api/v1/va/sse/register 239 84 ms 4.64 s 9.2%
GET /api/v1/va/work-orders/:id/wo-tasks 136 267 ms 4.70 s 2.2%
DELETE /api/v1/va/sse/register 126 55 ms 606 ms 0.0%
GET /api/v1/va/work-order-emails/:id 94 203 ms 1.21 s 1.1%
GET /api/v1/va/work-order-emails 91 331 ms 986 ms 0.0%
GET /api/v1/va/work-order-templates 60 141 ms 710 ms 0.0%
GET /api/v1/va/file-upload-emails 51 131 ms 270 ms 19.6%
GET /api/v2/va/work-order-configs/:id 48 234 ms 1.75 s 2.1%
POST /api/v2/va/agents/work-order-config/run 44 13.53 s 41.20 s 0.0%
GET /api/v1/va/work-orders/wo-activities/:id 43 125 ms 291 ms 0.0%
GET /api/v1/va/proxy/image 33 179 ms 410 ms 21.2%
POST /api/v1/va/mailgun/ai 33 1.03 s 4.49 s 0.0%
GET /api/v1/va/work-orders/:id/documents 28 244 ms 1.07 s 3.6%
GET /api/v1/va/work-order-templates/entity-types 21 30 ms 43 ms 0.0%
POST /api/v2/va/work-order-configs/event-scope-recipients 17 140 ms 746 ms 0.0%
GET /api/v1/va/edl/events/:id/plan 16 731 ms 2.19 s 18.8%
POST /api/v1/va/work-orders/:id/wo-activities 16 304 ms 2.68 s 0.0%
GET /api/v1/va/file-upload-emails/filter-values 15 140 ms 261 ms 0.0%
PUT /api/v1/va/work-orders/wo-activities/:id 10 2.75 s 8.17 s 0.0%
GET /api/v1/va/skills 9 78 ms 184 ms 0.0%
POST /api/v2/va/work-order-configs 8 510 ms 741 ms 0.0%
GET /api/v1/va/work-orders 7 1.57 s 2.17 s 0.0%
GET /api/v1/va/work-order-configs 6 1.23 s 1.79 s 16.7%
GET /api/v1/va/work-order-configs/:id 5 199 ms 276 ms 0.0%
GET /api/v1/va/work-order-templates/:id 5 130 ms 193 ms 0.0%
GET /api/v1/va/skills/activity 4 386 ms 670 ms 0.0%
GET /api/v1/va/work-orders/:id/wo-activities 4 274 ms 672 ms 0.0%
GET /api/v1/va/steer/:id 3 143 ms 286 ms 0.0%
GET /api/v1/va/work-order-configs/counts 3 158 ms 279 ms 0.0%
GET /api/v1/va/work-orders/:id/activities 2 24 ms 24 ms 100.0%
POST /api/v1/va/steer 2 7.12 s 13.98 s 0.0%
POST /api/v2/va/work-order-configs/:id/recipients 2 276 ms 317 ms 0.0%
POST /api/v2/va/work-order-configs/translate-email 2 13.03 s 13.20 s 0.0%
GET /api/v1/va/work-orders/wo-tasks/:id/subtasks 1 283 ms 283 ms 0.0%
PATCH /api/v1/va/steer/:id/reported 1 107 ms 107 ms 0.0%
PATCH /api/v1/va/work-orders/:id 1 23 ms 23 ms 100.0%
PATCH /api/v1/va/work-orders/:id/wo-activities/:id 1 20 ms 20 ms 100.0%
POST /api/v1/va/edl/events/:id/plan/generate 1 12.54 s 12.54 s 0.0%
POST /api/v1/va/steer/:id/approve 1 5.78 s 5.78 s 0.0%
POST /api/v1/va/steer/check 1 1.12 s 1.12 s 0.0%
PUT /api/v1/va/work-orders/:id 1 751 ms 751 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.