Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 7 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 17:32:53.
› →|
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.
← query trends

Query shape trend

plan 0A4540E4 · service workplansvc · write · last 7d

Query
CREATE (a:WorkPlanContext{deltimestamp:$a_deltimestamp}) 
SET a.createdat = timestamp(), a.updatedat = timestamp(), a.tildaid = randomUUID(), a.holdbitmap=?,a.holdbitmap=$a_holdbitmap,a.delpending=$a_delpending,a.workplanConfigId=$a_workplanConfigId,a.milestoneItemId=$a_milestoneItemId,a.jobId=$a_jobId,a.contextType=$a_contextType,a.configMilestoneItemId=$a_configMilestoneItemId,a.instanceMilestoneItemId=$a_instanceMilestoneItemId,a.orgAlias=$a_orgAlias,a.requestId=$a_requestId,a.checkpointGenId=$a_checkpointGenId,a.gateResolveGenId=$a_gateResolveGenId 
RETURN a.tildaid, a.createdat

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
0ms0.5ms1ms1.5ms2ms14 Nov 00:0016 Nov 00:0017 Nov 00:0000:00 1.9ms p9500:00 1.9ms p9500:00 1.9ms p95
p50 latency over time
Median elapsedTimeMs per bucket
0ms0.5ms1ms1.5ms14 Nov 00:0016 Nov 00:0017 Nov 00:0000:00 1.3ms p5000:00 1.1ms p5000:00 1.2ms p50
Executions / bucket
How often this shape ran
01k2k3k4k5k14 Nov 00:0016 Nov 00:0017 Nov 00:0000:00 3k00:00 4.5k00:00 2.3k

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.