Xray
hourly rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 3 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-20 13:05:15.
› →|
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 50 endpoints

Endpoint-level X-ray over the last 3d — 6,892 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
76k
3.4 per request · 413 slow
owner · on-call
Sambasiva Bandarupalli
backup Ahmed Aburaed · CODEOWNERS /data-science/
Endpoint Calls ▴ Avg latency Max Err %
PATCH /api/v1/va/work-orders/wo-tasks/:id/subtasks/:id 1 95 ms 95 ms 100.0%
DELETE /api/v1/va/work-order-configs/:id 2 1.74 s 1.83 s 0.0%
GET /api/v1/va/sse/register 2 32 ms 34 ms 0.0%
POST /api/v1/va/work-order-configs/:id/send-drafts 2 — — 0.0%
POST /api/v1/va/work-orders/:id/documents/:id/resolve 2 2.31 s 2.88 s 0.0%
POST /api/v2/va/work-order-configs/:id/transition 2 213 ms 267 ms 0.0%
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/wo-tasks/:id/reactivate 3 637 ms 742 ms 0.0%
POST /api/v1/va/mailgun/bounce 4 76 ms 272 ms 50.0%
POST /api/v2/va/work-order-configs/event-scope-recipients 4 1.51 s 3.08 s 0.0%
GET /api/v1/va/work-orders/wo-activities/:id 5 142 ms 262 ms 0.0%
POST /api/v1/va/mailgun/permanent-failure 5 295 ms 1.43 s 40.0%
GET /api/v1/va/skills 6 129 ms 354 ms 0.0%
POST /api/v1/va/mailgun/inbound 6 453 ms 770 ms 0.0%
POST /api/v1/va/work-orders/wo-tasks/:id/discard 6 363 ms 1.13 s 50.0%
POST /api/v2/va/work-order-configs/:id/recipients 6 316 ms 475 ms 0.0%
GET /api/v1/va/work-order-emails/:id 7 531 ms 1.68 s 28.6%
GET /api/v1/va/work-order-configs/:id 8 182 ms 421 ms 0.0%
POST /api/v1/va/work-order-templates 8 130 ms 365 ms 0.0%
GET /api/v1/va/proxy/image 9 38 ms 162 ms 88.9%
GET /api/v1/va/edl/events/:id/plan 11 479 ms 1.83 s 0.0%
GET /api/v1/va/work-orders/:id/changelogs/export 14 97 ms 229 ms 0.0%
GET /api/v1/va/file-upload-emails/filter-values 15 349 ms 1.01 s 0.0%
PUT /api/v2/va/work-order-configs/:id 16 181 ms 378 ms 0.0%
POST /api/v1/va/work-orders/:id/wo-activities 17 194 ms 855 ms 0.0%
GET /api/v1/va/work-order-emails 20 513 ms 1.09 s 15.0%
GET /api/v1/va/work-orders/wo-tasks/:id/subtasks 23 180 ms 1.26 s 0.0%
DELETE /api/v1/va/sse/register 24 90 ms 816 ms 0.0%
PUT /api/v1/va/work-orders/wo-tasks/:id 24 497 ms 1.59 s 33.3%
GET /api/v1/va/work-orders/:id/changelogs 28 118 ms 270 ms 0.0%
PUT /api/v1/va/work-orders/wo-activities/:id 32 1.64 s 12.93 s 0.0%
GET /api/v1/va/work-order-templates/entity-types 41 32 ms 79 ms 0.0%
POST /api/v2/va/work-order-configs/translate-email 41 5.49 s 16.64 s 9.8%
PUT /api/v1/va/work-orders/:id 42 5.12 s 2.2 min 21.4%
POST /api/v1/va/mailgun/ai 52 1.94 s 11.50 s 0.0%
POST /api/v1/va/identify-doctype/classify-document-id 55 9 ms 17 ms 100.0%
GET /api/v1/va/file-upload-emails 75 218 ms 1.01 s 0.0%
POST /api/v2/va/work-order-configs 84 501 ms 8.34 s 0.0%
GET /api/v1/va/work-orders/:id/documents 90 128 ms 920 ms 0.0%
GET /api/v1/va/work-orders/:id/wo-activities 94 174 ms 4.76 s 0.0%
GET /api/v1/va/work-order-templates 159 176 ms 4.01 s 0.0%
POST /api/v2/va/agents/work-order-config/run 184 10.50 s 42.83 s 2.2%
GET /api/v1/va/work-orders/:id/wo-tasks 215 197 ms 5.34 s 0.0%
GET /api/v1/va/sse/stream 257 — — 0.0%
POST /api/v1/va/sse/register 270 156 ms 4.65 s 0.7%
GET /api/v1/va/work-orders/:id/wo-activities/recent 372 253 ms 4.69 s 0.0%
GET /api/v2/va/work-order-configs/:id 524 215 ms 2.10 s 0.0%
GET /api/v2/va/work-order-configs 1,832 271 ms 5.49 s 0.0%
GET /api/v1/va/work-orders/:id 2,187 111 ms 4.41 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.