TenantAtlas/specs/053-unify-runs-monitoring/quickstart.md

Quickstart: Unified Operations Runs + Monitoring Hub (053)

Goal

Provide a single Monitoring/Operations area (view-only) to observe tenant-scoped long-running runs with consistent status semantics, safe failure visibility, and links to related artifacts. Phase 1 scope includes Drift generation and Backup Set “Add Policies”.

Local development

• Bring Sail up: ./vendor/bin/sail up -d
• Run migrations: ./vendor/bin/sail artisan migrate
• Run a queue worker (separate terminal): ./vendor/bin/sail artisan queue:work

Testing

Run the most relevant tests first:

• Tenant scoping for runs: ./vendor/bin/sail artisan test tests/Feature/RunAuthorizationTenantIsolationTest.php
• Drift generation run dispatch: ./vendor/bin/sail artisan test tests/Feature/Drift/DriftGenerationDispatchTest.php
• Drift job notifications + failure details: ./vendor/bin/sail artisan test tests/Feature/Drift/GenerateDriftFindingsJobNotificationTest.php
• Backup Set “Add Policies” job orchestration: ./vendor/bin/sail artisan test tests/Feature/BackupSets/AddPoliciesToBackupSetJobTest.php
• Status bucket semantics: ./vendor/bin/sail artisan test tests/Unit/BulkOperationRunStatusBucketTest.php

Operational notes

• Monitoring pages must remain DB-only (no external tenant calls on render).
• Run failures must stay sanitized and must not contain secrets/tokens.
• Ensure queue workers are running in staging/production so runs complete outside interactive sessions.