Review your monitor deployments
Overview
Section titled “Overview”Appwarden deploys one monitor for each hostname in your domain configuration. A monitor is a Cloudflare Worker that reports changes to that hostname’s DNS records and website responses, and it is what detects the incidents described in Declare and manage incidents.
The Monitors page in the Appwarden dashboard lists one card per deployment, with the state of each.
Monitors are not created or deleted by hand. You change your configuration files in Git, and Appwarden deploys, updates, or tears down the monitors that follow from the change.
Read a monitor card
Section titled “Read a monitor card”Each card shows:
- Status — one of the states in the table below
- Hostname — links to the live site
- Version — the monitor version currently deployed
- Configuration link — opens the domain configuration file in GitHub, at the commit that last deployed this monitor
- Active incidents — the DNS and website checks that are currently failing, with a link to the Discord thread for each, when one exists
- Last attempt — when the last deploy or deletion attempt ran. It appears only on failures, and it is how you tell a monitor that failed once from one that has been failing for hours
Deployment states
Section titled “Deployment states”| Status | Meaning |
|---|---|
| Healthy | The monitor is deployed and no check is failing |
| Alerting | The monitor is deployed and at least one incident is active |
| Deploying | A deployment is in progress, including a retry |
| Failed | The deployment did not complete. Appwarden retries it, and Last attempt shows when the last attempt ran |
| Pending deletion | Your configuration no longer includes this hostname. The deletion is queued but has not run yet |
| Deleted | The deletion completed and the Worker is gone. This is a final state, not a failure |
| Deletion failed | The deletion did not complete. The deletion job retries it, and Last attempt shows when it last tried |
| Verification Required | A button rather than a badge: the domain is not yet verified, so the monitor cannot check it. It links to Settings > Security; see Verify your setup |
Healthy and Alerting are both “deployed”. Which one a card shows depends on whether any incident is open against that hostname, so a successful deploy can land on either.
You can filter the page to All monitors, Deploying, Healthy, or Issue, and the counters above the list show the totals for each.
What happens when you remove a hostname
Section titled “What happens when you remove a hostname”Deleting a monitor is a configuration change, not a dashboard action. Remove the hostname’s configuration file, or the monitors entries for it, and merge the change to your default branch:
- Appwarden records the removal, and the card changes to Pending deletion
- The deletion job tears down the monitor’s Worker, and the card changes to Deleted
The card stays in the list so the deletion is visible while it happens. Neither state needs anything from you.
If the deletion fails, the card shows Deletion failed and the deletion job retries it. Check Last attempt before intervening: a monitor that has been failing for hours is a different problem from one that failed a minute ago.
What happens when a deployment fails
Section titled “What happens when a deployment fails”Appwarden retries a failed deployment. Start with the pull request that deployed it, since a configuration error is the usual cause, and check the workflow run in your domain configuration repository for the build log.
If the failure repeats, the card keeps showing Failed with a fresher Last attempt each time. A hostname with no successful deploy is not monitored, and no incident can be raised against it.
