Xray
hourly rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 48 hours▾
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:20:52.
› →|
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 31 endpoints

Endpoint-level X-ray over the last 48h — 776 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
2d ago
automated · 40d07ba1
Neo4j footprint
11k
3.4 per request · 175 slow
owner · on-call
Sambasiva Bandarupalli
backup Ahmed Aburaed · CODEOWNERS /data-science/
Endpoint Calls ▴ Avg latency Max Err %
GET /api/v1/va/work-order-configs 1 1.79 s 1.79 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%
POST /api/v1/va/mailgun/ai 1 4.49 s 4.49 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/wo-activities/:id 1 2.12 s 2.12 s 0.0%
GET /api/v1/va/work-orders 2 1.92 s 2.17 s 0.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/edl/events/:id/plan 3 960 ms 1.93 s 0.0%
GET /api/v1/va/steer/:id 3 143 ms 286 ms 0.0%
GET /api/v1/va/work-order-templates/:id 3 127 ms 193 ms 0.0%
POST /api/v2/va/work-order-configs 3 533 ms 741 ms 0.0%
GET /api/v1/va/work-order-configs/:id 4 181 ms 276 ms 0.0%
GET /api/v1/va/work-order-templates/entity-types 4 34 ms 41 ms 0.0%
GET /api/v1/va/work-order-emails/:id 5 693 ms 1.21 s 0.0%
GET /api/v1/va/proxy/image 7 207 ms 311 ms 0.0%
POST /api/v2/va/work-order-configs/event-scope-recipients 7 162 ms 578 ms 0.0%
GET /api/v1/va/work-orders/:id/documents 13 133 ms 535 ms 7.7%
POST /api/v2/va/agents/work-order-config/run 13 19.98 s 41.20 s 0.0%
GET /api/v1/va/work-order-templates 15 179 ms 710 ms 0.0%
DELETE /api/v1/va/sse/register 26 65 ms 183 ms 0.0%
GET /api/v1/va/work-orders/:id/wo-tasks 28 432 ms 3.96 s 0.0%
GET /api/v2/va/work-order-configs/:id 28 191 ms 1.75 s 3.6%
GET /api/v1/va/work-orders/:id/wo-activities/recent 56 526 ms 6.24 s 0.0%
GET /api/v1/va/sse/stream 59 — — 0.0%
POST /api/v1/va/sse/register 73 61 ms 200 ms 13.7%
GET /api/v1/va/work-orders/:id 186 139 ms 4.69 s 0.5%
GET /api/v2/va/work-order-configs 225 378 ms 3.08 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.