Uptime, errors and status pages
Everything here lives in Project › Monitoring, and alerts are set up once per workspace in Settings › Alerts.
Uptime monitors#
Click Monitor <your URL> and HostEdge checks your production URL every few minutes, starting right away. Add monitor checks any other address: an API, a health endpoint, a third-party service you depend on.
A check passes when the URL answers with a status below 400 within 10 seconds (and, if you set one, the page contains your keyword). After two failed checks in a row the monitor is down: an incident opens and your alert channels hear about it. The first passing check resolves the incident and sends a "back up" alert with how long it was down.
On the Starter plan and up, turn on Check from 3 regions (when adding a monitor, or from its menu). Each check then runs from North America, Europe and Asia-Pacific, and a check fails only when most regions fail, so a network problem in one region is not reported as an outage. Failed checks list how each region did.
Each monitor shows uptime for 24 hours, 7 and 30 days, the average response time, a response-time chart for the last day, 90 days of daily bars and the recent failed checks.
| Plan | Monitors per project | Checked as often as every |
|---|---|---|
| Free | 2 | 5 minutes |
| Starter | 10 | 1 minute |
| Pro | 50 | 1 minute |
| Agency | 100 | 1 minute |
Errors#
Exceptions thrown by your Worker and console.error lines are grouped by their message, with numbers, IDs, quoted values and URLs ignored, so User 42 not found and User 7 not found are one error. Each group shows how often it happened, when it was first and last seen, and the last path. Stack trace and request opens the stack frames of the latest occurrence (when the runtime reports them), the request it happened in (method, path, status, country) and the deployment.
Resolve an error once it is fixed: if it happens again, it reopens and you get an alert, because a regression is worth knowing about. Ignore keeps an error out of your way and out of your alerts. Logs opens the matching log lines.
Status page#
In Monitoring › Status page, publish a page at https://hostedge.app/status/<name> that shows your monitors with 90 days of uptime, current incidents and past ones. Share it with your users, or link it from your site's footer.
To serve it from your own address, enter a domain such as status.example.com under Custom domain once the page is published, and create the CNAME record shown. The page goes live there when the domain verifies; it counts as one of your plan's custom domains and appears on the Domains page with a Status page badge.
Monitors open and resolve incidents on their own. You can also Report an incident by hand (for example, a slow payment provider) and post updates as it moves from Investigating to Identified, Monitoring and Resolved.
Alerts#
Add channels in Settings › Alerts (admins and owners):
- Email: any address.
- Slack: an incoming webhook URL (Slack › Apps › Incoming Webhooks).
- Discord: a channel webhook URL (Channel settings › Integrations › Webhooks).
- Telegram: a bot token from @BotFather and the chat ID.
- SMS (Starter plan and up): a phone number in international format. HostEdge texts it a 6-digit code; alerts go to it once you enter the code. Up to 50 texts a day per workspace.
Pick the events each channel gets: a monitor goes down or comes back, a new or returning error, a cron job failing three times in a row, a failed deployment. A channel can cover every project or only some. Send test checks the connection; if a delivery fails, the channel shows the last error. Webhook URLs, bot tokens and phone numbers are stored encrypted and never shown again.
Escalation and quiet hours#
Each channel can wait before it gets "monitor down": If still down after 5, 15, 30 or 60 minutes. Use it to escalate, for example Slack right away and SMS only when an outage lasts. A delayed channel hears about each outage once, and gets "back up" only if it heard the site was down.
Quiet hours (from, to, time zone) hold every alert except "monitor down" during those hours, so a new error at 3 a.m. waits in the dashboard while an outage still wakes you up.