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 18:08:38.
› →|
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

dashql 26 endpoints

Endpoint-level X-ray over the last 3d — 250 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.50% derived · 0.0× burn
p95 vs normal
—
no baseline yet
last deploy
2d ago
automated · e4eb245d
Neo4j footprint
313
1.2 per request · 10 slow
owner · on-call
Vishal Karedla
backup Taylor Futral · CODEOWNERS /dashQL/
Endpoint Calls ▾ Avg latency Max Err %
POST /api/dashql 186 1.15 s 3.73 s 0.0%
POST /api/dashql/charts/staging_docs_processed 4 2.08 s 2.24 s 0.0%
POST /api/dashql/charts/staging_docs_uploaded_by_month 4 2.26 s 2.51 s 0.0%
POST /api/dashql/charts/staging_docs_uploaded_by_source 4 2.65 s 2.93 s 0.0%
POST /api/dashql/charts/staging_document_funnel 4 2.71 s 4.03 s 0.0%
POST /api/dashql/charts/staging_document_stats 4 2.64 s 4.75 s 0.0%
POST /api/dashql/charts/staging_processing_activity_matrix 4 2.21 s 2.34 s 0.0%
POST /api/dashql/charts/staging_processing_activity_total 4 1.78 s 2.08 s 0.0%
POST /api/dashql/charts/staging_qc_by_category 4 2.37 s 2.66 s 0.0%
POST /api/dashql/charts/staging_qc_by_severity 4 2.25 s 2.68 s 0.0%
POST /api/dashql/charts/staging_qc_document_count 4 2.63 s 2.75 s 0.0%
POST /api/dashql/charts/staging_status_breakdown 4 2.05 s 2.23 s 0.0%
POST /api/dashql/charts/staging_submission_timeliness_matrix 4 2.62 s 2.97 s 0.0%
POST /api/dashql/charts/staging_submission_timeliness_total 4 2.09 s 2.90 s 0.0%
POST /api/dashql/charts/ai_accuracy_matrix 1 2.01 s 2.01 s 0.0%
POST /api/dashql/charts/ai_findings_by_category 1 1.94 s 1.94 s 0.0%
POST /api/dashql/charts/document_accuracy_matrix 1 2.02 s 2.02 s 0.0%
POST /api/dashql/charts/document_accuracy_overall 1 2.25 s 2.25 s 0.0%
POST /api/dashql/charts/recommendation_state_counts 1 2.42 s 2.42 s 0.0%
POST /api/dashql/charts/staff_accountability 1 3.27 s 3.27 s 0.0%
POST /api/dashql/charts/staff_uploaders 1 1.78 s 1.78 s 0.0%
POST /api/dashql/charts/work_orders_draft_outcomes 1 1.68 s 1.68 s 0.0%
POST /api/dashql/charts/work_orders_follow_up_by_site 1 1.75 s 1.75 s 0.0%
POST /api/dashql/charts/work_orders_summary 1 1.82 s 1.82 s 0.0%
POST /api/dashql/charts/work_orders_table 1 1.95 s 1.95 s 0.0%
POST /api/dashql/charts/zone_accountability 1 1.81 s 1.81 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.