Documentation
Back to tutorials

Operations

Ops Health Use Cases

Use Operations Health to understand bot/web status, Discord reachability, notification delivery, OCR runtime, RaidHelper, tickets, and recent trouble spots.

Who uses it

Managers, super admins, support-minded staff

Where it lives

Dashboard > Operations

Goal

Staff can separate real incidents from normal noise and send maintenance messages when needed.

Before You Start

  • Operations or manager-level dashboard access.
  • Configured channels and modules you want to monitor.

Steps

1

Check process and service health

Start with bot and web heartbeat status. A stale heartbeat means the process may be down or not publishing health data.

2

Review Discord reachability

Use channel and role checks to spot permission or deletion problems. If a configured destination is unreachable, fix Discord permissions or update GearCheck settings.

3

Inspect module health

OCR runtime, RaidHelper API, notification delivery, support ticket load, and inbox state each point to a different operational problem. Follow the module with the warning, not every card at once.

4

Use maintenance notices intentionally

Send downtime or maintenance messages only when staff need to communicate a real issue. Notices should be targeted to the relevant channels and recorded in the event ledger.

Launch Checklist

  • Warnings map to a specific action.
  • Configured channels still exist and are reachable.
  • Recent trouble spots are not just expected startup noise.
  • Maintenance notices were sent only to intended destinations.

Common Pitfalls

  • Treating every warning as an outage.
  • Sending broad maintenance notices for a single-channel issue.
  • Ignoring stale configured channels after Discord cleanup.

Related