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 22:50:04.
› →|
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 28 endpoints

Endpoint-level X-ray over the last 5d — 2,361 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
[email protected] · 6db9855a
Neo4j footprint
104k
9.0 per request · 1143 slow
owner · on-call
Sambasiva Bandarupalli
backup Ahmed Aburaed · CODEOWNERS /data-science/
Endpoint Calls ▴ Avg latency Max Err %
PATCH /api/v1/va/work-order-templates/:id 1 115 ms 115 ms 100.0%
POST /api/v1/va/work-order-configs/:id/send-drafts 1 — — 0.0%
POST /api/v1/va/work-orders/:id/wo-activities 1 347 ms 347 ms 0.0%
POST /api/v1/va/work-orders/:id/wo-activities/:id/regenerate-email 1 113 ms 113 ms 0.0%
POST /api/v2/va/work-order-configs/:id/recipients 1 265 ms 265 ms 0.0%
GET /api/v1/va/work-order-templates/:id 5 54 ms 119 ms 0.0%
GET /api/v1/va/work-orders/:id/forms 5 116 ms 317 ms 0.0%
POST /api/v1/va/mailgun/ai 7 2.08 s 7.72 s 0.0%
GET /api/v1/va/work-orders 14 200 ms 1.24 s 35.7%
GET /api/v1/va/proxy/image 15 118 ms 176 ms 100.0%
GET /api/v1/va/file-upload-emails/filter-values 21 125 ms 400 ms 28.6%
GET /api/v1/va/work-order-templates/entity-types 25 35 ms 103 ms 0.0%
GET /api/v1/va/file-upload-emails 35 144 ms 569 ms 28.6%
PUT /api/v1/va/work-orders/wo-activities/:id 45 3.96 s 10.89 s 0.0%
POST /api/v2/va/work-order-configs 46 454 ms 4.51 s 0.0%
POST /api/v1/va/mailgun/inbound 53 1.04 s 2.70 s 0.0%
GET /api/v1/va/work-orders/:id/wo-tasks 62 294 ms 3.48 s 0.0%
DELETE /api/v1/va/sse/register 69 89 ms 910 ms 2.9%
GET /api/v1/va/work-orders/:id/wo-activities 102 270 ms 646 ms 0.0%
POST /api/v2/va/agents/work-order-config/run 115 12.16 s 25.49 s 0.0%
GET /api/v1/va/work-orders/:id/wo-activities/recent 124 381 ms 4.84 s 0.0%
GET /api/v1/va/work-order-templates 134 97 ms 606 ms 0.0%
GET /api/v1/va/work-orders/:id 155 240 ms 4.58 s 0.0%
POST /api/v1/va/sse/register 161 74 ms 405 ms 4.3%
GET /api/v1/va/sse/stream 177 — — 30.5%
GET /api/v2/va/work-order-configs/:id 189 210 ms 1.25 s 0.0%
GET /api/v1/va/work-orders/:id/documents 310 278 ms 1.64 s 0.0%
GET /api/v2/va/work-order-configs 487 445 ms 9.36 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.