Guide
Setting up uptime monitoring
Get alerted the moment a site goes down, with screenshots at failure and recovery.
4 min read
What uptime monitoring does
Destiny QA checks every monitored project once per minute using an HTTP request to the project's base URL. If the site returns an error status or does not respond within 10 seconds, an incident is recorded and alerts are sent. When the site comes back, the incident is closed and a recovery alert goes out.
Enable monitoring for a project
Open the Monitoring section from the sidebar and find the project you want to monitor. Click through to the project monitoring page and toggle Enable monitoring on. Monitoring starts on the next scheduler tick, within 60 seconds.
Set up email alerts
Enter an alert email address in the settings card. Destiny QA sends one email when the site first goes down and another when it recovers, including the total downtime duration. You do not receive repeated emails while the site stays down.
Set up Slack alerts
If your account has a Slack workspace connected, you can turn on Slack alerts for each project. Select the channel you want alerts posted to from the dropdown. Down alerts include a screenshot of what the browser rendered at the time of failure. Recovery alerts include the total downtime. If Slack is not connected to your account, the toggle remains disabled until you connect it under Account Settings.
How screenshots work
One screenshot is taken the first time a failure is detected, showing exactly what the browser rendered at that moment. No further screenshots are taken while the site remains down. When the site recovers, a second screenshot is taken 3 minutes later to confirm the site is fully loaded, not just reachable. Both screenshots appear in the incident history on the project monitoring page.
Reading the incident history
The project monitoring page shows a table of past incidents with the time the site went down, the time it recovered, and the total duration. Each incident shows the HTTP status or error message recorded at failure, alongside the before and after screenshots. The uptime percentage shown is calculated over the last 30 days.
What counts as down
Destiny QA treats any HTTP status of 500 or above as a failure, as well as connection errors and timeouts. Status codes below 500, including redirects, are treated as up. This means a site that redirects correctly is not flagged as down.