Deployment readiness history

Read-only retained deployment-readiness snapshots with default latest-vs-previous mode, optional manual snapshot comparison, and additive filters.

Read-only readiness history

These snapshots come from operator-run fleet scripts. The dashboard only reads them and does not refresh readiness, install secrets, or change infrastructure state.

Generated dir: /secure/muzorg/digitalocean/generated

Manual readiness snapshot compare

Choose two retained readiness snapshots. Changes are shown from the left snapshot to the right snapshot.

Leave the selector blank to keep the default latest-vs-previous readiness comparison mode.

Readiness filters

Narrow the current readiness comparison by employee, readiness state, or transition without changing the underlying retained snapshots.

Default comparison mode

This view compares the newest retained deployment-readiness snapshot to the one immediately before it.

Previous readiness snapshot

Immediately previous retained readiness snapshot

Latest readiness snapshot

Latest retained readiness snapshot

Fleet blocker rollup

Fleet-wide blocker visibility for the selected readiness comparison. This panel stays read-only and groups blocked VMs by cause, streak length, and recovery status.

Currently blocked

0

Newly blocked

0

Still blocked

0

Recovered

0

Changed blocker

0

waiting on secrets

0

No employees currently blocked by this cause.

secret mismatch

0

No employees currently blocked by this cause.

runtime unreachable

0

No employees currently blocked by this cause.

image unresolved

0

No employees currently blocked by this cause.

unknown

0

No employees currently blocked by this cause.

  • - Fleet manifest not found at /secure/muzorg/digitalocean/fleet.production.yaml.
  • - Health artifact data is missing.
  • - Inventory artifact data is missing.
  • - No previous deployment readiness snapshot is available for blocker comparison yet.
  • - No retained deployment readiness snapshots are available yet.
  • - Smoke artifact data is missing.

Longest active blocker streaks

Consecutive retained readiness snapshots with the same blocker cause. Running and staged states break the streak.

EmployeeCauseStatusStreakStartedActions
No currently blocked employees appear in the selected current readiness snapshot.

Recent blocker changes

Newly blocked, recovered, changed-blocker, and incomplete blocker comparisons from the selected snapshot pair.

EmployeeStatusPreviousCurrentSummary
No blocker changes were detected for the selected readiness comparison.

Filtered readiness view

Filtered counts are derived from the current readiness comparison. They do not change the underlying snapshot diff.

Default compare + filtered view
State: secret mismatch

Rows before filter

0

Rows after filter

0

Improved

improved

0

Regressed

regressed

0

Filtered previous-state counts

No previous-state rows matched the active filters.

Filtered current-state counts

No current-state rows matched the active filters.

No readiness transitions match the active filters.

Deployment readiness history

Latest-vs-previous deployment-readiness comparison plus retained readiness snapshots. This is read-only visibility built from generated artifacts.

Snapshots

0

Improved

0

Regressed

0

Unchanged

0

Missing data

0

Latest readiness snapshot

Not recorded

No retained snapshot

Missing

Previous readiness snapshot

Not recorded

No retained snapshot

Missing

Newly running

improved

0

Regressions

regressed

0

Blocked

unknown

0

Unchanged

unchanged

0

SnapshotRowsWarningsState countsRaw
No retained deployment-readiness snapshots are available yet.

Readiness warnings

Missing history, invalid filters, and incomplete comparison data are surfaced explicitly instead of being hidden.

  • - Fleet manifest not found at /secure/muzorg/digitalocean/fleet.production.yaml.
  • - Health artifact data is missing.
  • - Inventory artifact data is missing.
  • - No previous deployment readiness snapshot is available for comparison yet.
  • - No readiness transitions match the active filters.
  • - No retained deployment readiness snapshots are available yet.
  • - Smoke artifact data is missing.

Newly running

VMs that now classify as running and were not running in the previous retained snapshot.

EmployeeTransitionPreviousCurrentSummary
No readiness transitions match the active filters.

Newly staged

VMs that now look staged compared with the previous retained snapshot.

EmployeeTransitionPreviousCurrentSummary
No readiness transitions match the active filters.

Newly waiting on secrets

VMs that moved into a missing-secrets state.

EmployeeTransitionPreviousCurrentSummary
No readiness transitions match the active filters.

Newly secret mismatch

VMs whose installed secret file now mismatches the expected bundle.

EmployeeTransitionPreviousCurrentSummary
No readiness transitions match the active filters.

Newly runtime unreachable

VMs that had secrets installed but now fail runtime reachability checks.

EmployeeTransitionPreviousCurrentSummary
No readiness transitions match the active filters.

Newly image unresolved

VMs whose configured image source no longer resolves cleanly.

EmployeeTransitionPreviousCurrentSummary
No readiness transitions match the active filters.

Regressed

VMs whose readiness rank fell between the previous and latest retained snapshot.

EmployeeTransitionPreviousCurrentSummary
No readiness transitions match the active filters.

Unchanged

VMs whose readiness state stayed the same across the compared retained snapshots.

EmployeeTransitionPreviousCurrentSummary
No readiness transitions match the active filters.

Missing comparison data

VMs that were present on only one side of the retained readiness comparison.

EmployeeTransitionPreviousCurrentSummary
No readiness transitions match the active filters.