Xray
hourly rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 48 hours▾
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 11:11:41.
› →|
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.

Attribution

Can every Neo4j statement be tied back to the request, user and service that caused it? automation · live scan of the query log

Every other view depends on this. Per-endpoint attribution comes from the trace id shared by the request log and the Neo4j statement; the foreground/background split comes from tx_origin. Where the metadata is missing, those views degrade quietly rather than visibly — which is why this is measured here.

scanning the Neo4j query log…

Every cluster

Measuring one cluster misleads. Clusters run different image lines, so the same service can be fully attributed on one and not at all on another — docsvc measured 100% on master and 0% on nexus purely because nexus ran a production-line image predating the instrumentation. Part of any gap therefore resolves as releases roll.

sampling every cluster…