Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 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-19 13:41:42.
› →|
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.

Change timeline 36

pushed 27h ago 36 shown authoritative back 75d

Everything that changed on nexus in the last 30d — what git deployed, what the cluster actually ran, and what someone changed by hand — with traffic, errors and latency for equal windows either side of each deploy. A deploy row is a commit in the config repo that ArgoCD applied; a ran row is the image a pod actually started, whose tag carries a commit from the service's own repo. Those are two different repositories, so each id says which it is and links to it. ?A deploy row compares the 60 minutes before the deploy with the 60 minutes after it, from the same rollups the charts read. Where the after-window is not complete yet the row says so rather than comparing unequal windows, which would manufacture a regression out of arithmetic.

How to read this page — change timeline

Three trails on one axis: what git deployed, what the cluster actually ran, and what someone changed by hand. They are kept apart rather than merged, because which kind a change was is usually the answer.

deploy
ArgoCD synced a commit for this app. This is what git ASKED for.
ran
A new pod template started — from the ReplicaSet trail, so it is what the cluster ACTUALLY ran. Usually right after a deploy; when it appears without one, something changed outside git.
outside git
A write straight to the cluster, from the audit log: a kubectl edit, a patched deployment, a deleted configmap. These are the ones worth reading first.
config <sha>
The commit in the config repo (ash-nazg) that ArgoCD applied. Links to that commit.
image / code
The container image that started, and the commit inside its tag — which is a commit in the SERVICE's own repo, a different repository from the config commit.
before → after
Traffic, p50, p95 and error rate for equal windows either side of the deploy, from the same rollups the charts read. Green is better, red worse, grey is inside ±5%.
too recent / too few samples
The comparison is refused rather than guessed: an after-window that is not complete yet, or fewer than 30 latency samples on one side.

What this page will not tell you

  • That a deploy CAUSED a change beside it. Both facts are true and adjacent; the causal claim is yours to make. Two deploys inside one window means two candidates.
  • Every change. ArgoCD keeps only its last 10 revisions per app, so anything older than this collector has been running is gone — the provenance chip says how far back the stored trail is authoritative.
  • Changes that produced no new pod template — a config value read at runtime, for instance — leave no `ran` row.
Columns
Views
Export CSV
Changes on nexus, newest first, with before-and-after figures for each deploy
When Kind Service Who What was applied (config commit · image · code commit) Before → after (±60m)
1d ago deploy docsvc autosync confige5f310be4 too few samples
2d ago deploy docproc autosync config6db9855a7 too few samples
2d ago deploy studiosvc autosync config5beaa388d too few samples
2d ago deploy regsvc autosync config5beaa388d too few samples
2d ago deploy tusker autosync config5beaa388d too few samples
2d ago deploy dashrsvc autosync config5beaa388d too few samples
2d ago deploy schedsvc autosync config5beaa388d too few samples
2d ago deploy workplansvc autosync config5beaa388d too few samples
2d ago deploy onboardingsvc autosync config5beaa388d too few samples
2d ago deploy patientsvc autosync config5beaa388d too few samples
2d ago deploy docsvc autosync config5beaa388d too few samples
2d ago deploy enrollsvc autosync config5beaa388d too few samples
2d ago deploy finsvc autosync config5beaa388d too few samples
2d ago deploy execsvc autosync config5beaa388d too few samples
2d ago deploy notifsvc autosync config5beaa388d too few samples
2d ago deploy dashql autosync config5beaa388d too few samples
3d ago deploy docproc autosync config0a6d44162 too few samples
3d ago deploy phase-2-nexus autosync config5137d4c7f too few samples
3d ago deploy docproc autosync config5137d4c7f too few samples
3d ago deploy docproc autosync config20c22bafe too few samples
3d ago deploy studiosvc-infra-nexus autosync confige56d681e9 too few samples
3d ago deploy execsvc autosync config5c4286938 too few samples
3d ago deploy studiosvc autosync config5c4286938 too few samples
3d ago deploy onboardingsvc autosync config5c4286938 too few samples
3d ago deploy docsvc autosync config5c4286938 too few samples
3d ago deploy patientsvc autosync config5c4286938 —
3d ago deploy phase-2-nexus autosync config5c4286938 —
3d ago deploy regsvc autosync config5c4286938 —
3d ago deploy finsvc autosync config5c4286938 —
3d ago deploy tusker autosync config5c4286938 —
3d ago deploy notifsvc autosync config5c4286938 —
3d ago deploy workplansvc autosync config5c4286938 —
3d ago deploy dashrsvc autosync config5c4286938 —
3d ago deploy schedsvc autosync config5c4286938 —
3d ago deploy dashql autosync config5c4286938 —
3d ago deploy enrollsvc autosync config5c4286938 —