Xray
all clusters 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 08:01:40.
› →|
updated 21h 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.

execsvc master

Everything that changed this service, however it got changed. ← all of master

Recorded deploys
12
12 automated
People who deployed
0
Oldest deploy kept?ArgoCD keeps only the last 10 revisions per application and drops the rest itself. Anything older than what X-ray has already collected is gone — which is why the collector runs on a schedule.
2026-11-14 15:19:13 UTC
nothing before this is recoverable

Everything that changed this service audit window 7d ~13s · 30d ~45s · 90d minutes · 400d very slow

Two sources on one timeline. sync rows come from ArgoCD's own history — who deployed, which git revision, and the image that revision rendered to. by hand rows come from the cluster's Kubernetes audit log: a kubectl edit never touches an Application, so ArgoCD has no record of it at any depth. They cannot duplicate each other, because ArgoCD's own writes arrive as a service account and are excluded. The table renders once, when both halves are in hand — a table that looked complete before the slower half arrived would be the one mistake worth avoiding here.

reading ArgoCD history and master's audit log…