Operator Runbook

This page is the working reference for ops.omnilux.tv.

Start of shift

At the beginning of an operator shift:

1. Sign in to ops.omnilux.tv
2. Verify your operator session is elevated with MFA
3. Review public service health for app, ops, relay, media, and cloud auth
4. Review recent operator activity and policy changes
5. Confirm the current managed-media operating mode is correct

Support flow

When investigating a customer issue:

1. Look up the cloud account
2. Review subscription state
3. Review managed-media entitlement
4. Review linked self-hosted servers
5. Review recent relay sessions and relay tokens
6. Leave a support note before closing the interaction

High-impact actions

These actions should only be taken from an MFA-elevated operator session:

• changing managed-media policy
• changing relay policy
• granting or removing operator access
• granting or removing explicit managed-media access
• revoking relay sessions
• revoking relay tokens
• changing managed-media operating state

Managed media incidents

When managed media is unhealthy:

1. Set the operating mode to degraded or maintenance
2. Publish a short incident message
3. Confirm the customer app reflects the current state
4. Track follow-up in the operator audit trail
5. Return the runtime to normal when the issue is resolved

Reliability checks

Keep these boring checks alive:

• service canary is green
• ops auth smoke is green
• relay health is current
• managed media runtime is still reporting heartbeats
• password-reset and support actions still work

Documentation links

Keep these nearby while operating the system:

• Cloud Product Contract
• Client Readiness
• Managed Media