Xray
all clusters 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-19 18:05:29.
› →|
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.

Who changed what 3 deploys

Every deploy ArgoCD has a record of, and the person behind it. environment person

Services in test26 1 · click one for its full history

Service DeploysPeopleBy handLast
studiosvc-infra-dev 3 1 0 2026-11-14 14:30:14 UTC

Deploys newest first

WhenEnvironmentAppWhoRevision
2026-11-14 14:30:14 UTC test26 studiosvc-infra-dev · infra [email protected] 160609b9b
2026-11-14 11:52:45 UTC test26 studiosvc-infra-dev · infra [email protected] 8c63aaf72
2026-11-14 10:51:22 UTC test26 studiosvc-infra-dev · infra [email protected] 8c63aaf72

manual only marks an app whose autoSync is off — a person is the only thing that can ever deploy it, so every one of those is a deliberate hand-sync. A failed sync never becomes a history entry, so this is the record of deploys that succeeded.

Changed without ArgoCD · test26 last max

A kubectl edit against a live workload never touches an Application, so it appears in no deploy above — it exists only in the cluster's audit log. Restarts (deleting pods) are not shown: the controller recreates them from the unchanged Deployment, so nothing declared has moved.

reading the cluster audit logs…

People in test26 1 · deploys = sync events, apps = distinct applications

PersonDeploysAppsBy handLast
[email protected] 3 1 0 2026-11-14 14:30:14 UTC only this