Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Max · 30 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-21 04:35:04.
› →|
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.
← query trends

Query shape trend

plan B5B0D3B7 · service (internal) · read · last max

Query
MATCH (d:Document)-[:DOC_TO_ORG]->(o:Organization) 
WHERE d.status IN $statuses 
OPTIONAL MATCH (d)-[:DOCUMENT_VERSION]->(v:DocumentVersion) 
WITH d, o, v 
ORDER BY v.createdat DESC 
WITH d, o, collect(v)[?] AS latest 
RETURN o.alias AS org, d.tildaid AS document_id, latest.tildaid AS version_id, d.fileName AS name, d.status AS status

Optimizer suggestions

No suggestion for this shape yet — generate one now and it will read this exact statement and its timings.

p95 latency over time
95th-percentile elapsedTimeMs per bucket
0ms1s2s3s4s5s00:0000:00 4.8s p95
p50 latency over time
Median elapsedTimeMs per bucket
0ms1s2s3s4s00:0000:00 3.5s p50
Executions / bucket
How often this shape ran
0100:0000:00 1

p50/p95 are recovered from the per-bucket latency histogram. A rising p95 with a flat p50 means the tail is getting slower (lock contention, GC, a cold cache) even when the typical case is fine.