Updated 25 October 2026 · By the Upcertain team
What to monitor
| Service | Monitor | Interval |
|---|---|---|
| Marketing site | HTTP | 1 to 5 min |
| App sign-in page | Keyword: text that appears only when it works | 30 s |
| Public API | HTTP on a health endpoint that checks the database | 30 s |
| Webhooks you send | Heartbeat from the delivery worker | per run |
| Billing, reports, exports | Heartbeat from each scheduled job | per run |
| Every certificate | Comes with HTTPS monitors | with the check |
Alert the owner, not everyone
- Give each team its own channel: the API in
#api-oncall, billing jobs in#billing. - Tune confirmation checks to your deploys, so a rolling restart does not page anyone. The deploy guide shows the numbers.
- Turn on alert grouping so a database outage arrives as one message listing every affected service.
- Send failures into your own tooling with signed webhooks.
Tell customers before they ask
A status page on status.yourproduct.com updates from the monitors on its own. Incidents that start together are shown as one with each service's downtime, brief blips fold into a daily line, and planned maintenance appears ahead of time. Customers can subscribe to the updates you publish.
Give your tools and agents access
The REST API lets your pipeline pause monitors during a migration or read incidents into a dashboard. The MCP server lets engineers ask Claude or Cursor what is down without leaving their editor.
A first week
- Day one: monitor the sign-in page, the API health endpoint and the marketing site, with alerts to one shared channel.
- Add heartbeats to the scheduled jobs customers would notice first: billing, exports, emails.
- Watch a few deploys in the check log and set confirmation checks just above how long they fail.
- Split alerts by owner once you know which services page which team.
- Publish the status page and link it from your app's help menu and error pages.
Roles that match your team
Owners and admins manage billing-sensitive settings and API keys; editors manage monitors and acknowledge incidents; viewers read; notify-only contacts get email alerts without a login. Team and Business include unlimited members.
What Upcertain does not do
It checks from one region (Seoul), and it has no browser transaction checks, phone or SMS alerts, or on-call schedules. Many SaaS teams pair it with an on-call tool through a webhook.