Browse
Getting Started
Roles & Permissions
Time Tracking
Invoices & Payments
Estimate Form Wizard
Accounting Engine
Accounts Receivable
Client Credits
A/R Aging
Collections
Statements
Report Interpretation
Profit & Loss
Balance Sheet
Trial Balance
A/P Aging
Storage & Files
Billing & Subscriptions
Real Estate Plan
RE Settlements Workflow
RE Commission Splits
RE Reporting
RE Follow-ups & Pipeline
RE Access Controls
Ops Console
Production Runbook
FAQ
The Ops Console is the staff-only operations cockpit. It’s designed to prevent “mystery failures” by surfacing checks, evidence, and environment posture.
Primary sections
- Ops Dashboard: company search + quick access to support workflows.
- Ops Checks: run smoke/invariants/idempotency/readiness + store evidence output.
- Launch Gate: ensure launch items are green before production cutover.
- Backups & Retention: record backup runs, prune old runs, track restore tests.
- Probes: test error + test alert to verify monitoring in production.
Recommended ops routine
- Run Ops → Checks → Run all after every deploy.
- Export recent runs as launch evidence and attach to release notes.
- Verify backups are running and record at least one restore test per environment.
- Use probes to confirm alerting paths work end-to-end.
Automated daily checks (recommended)
In production, schedule a daily run to capture continuous readiness evidence.
python manage.py ez360_run_ops_checks_daily(optionally include--company-idfor company-scoped checks)python manage.py ez360_prune_ops_check_runs --days 30(retention; keep Ops evidence lean)
Staff-only
Ops Console endpoints are restricted to staff. Keep access tight.