Managing Your Status Page

After initial deployment, you can manage your setup in two ways:

• through the deployed status page's admin panel,
• by re-running the wizard and loading existing config.

Accessing the admin panel

Navigate to https://your-status-page-url/admin in your browser. Log in with the admin credentials you set during deployment.

From the admin panel you can create incidents, schedule maintenance, and manage your status page without touching the wizard.

Creating incidents

When a service issue occurs, create an incident from the admin panel:

• Title -- a short summary visible on the status page (e.g. "API latency degradation").
• Message -- additional detail about the issue and its impact.
• Affected monitors -- select which monitors are impacted. Their status indicators will update on the public page.
• Severity -- choose the severity level that reflects the impact (e.g. minor, major, critical).

Incidents are visible to anyone viewing your status page as soon as they are created.

Resolving and updating incidents

As the situation evolves, post updates to an active incident to keep your users informed. Each update is timestamped and displayed in the incident timeline on the status page.

When the issue is resolved, mark the incident as resolved. The affected monitors return to their normal status based on the next successful check.

Scheduling maintenance

Plan ahead by creating maintenance windows with a start and end time. Scheduled maintenance appears on the status page before it begins, so users know what to expect. During the window, affected monitors show a maintenance status instead of triggering alerts.

Viewing uptime history

The status page shows uptime percentage and latency graphs for each monitor. Historical data is stored in your flarewatch-state KV namespace and persists across updates unless you explicitly reset it.

Common post-deploy tasks

• Add/update/remove monitors
• Update branding (title, logo, theme, custom CSS)
• Change webhook target/template
• Adjust auth settings (admin/status page protection)
• Update custom-domain settings

Updating safely

When existing config is loaded, deployment metadata is reused so updates are incremental (not a fresh blank deployment). State/history is preserved by default unless you explicitly choose to reset it.