Group
  • Deployment

    Set up uptime monitoring for the paths that actually matter

    Monitor the flows users care about, not just a homepage ping that stays green while checkout is broken.

    • Improve quality
    • Plan & validate
    • Beginner
    • General

Free Prompt

Set up external uptime monitoring for my app. A hosted service (UptimeRobot, BetterStack, Checkly, Pingdom, or similar) is fine; the goal is that when the site goes down at 3am I hear about it in minutes. Set these up: 1. Monitor more than the homepage. Add checks for the routes that matter: sign-in, dashboard, checkout, the main API endpoint. A homepage that stays green while checkout returns 500s is worse than no monitor at all. 2. For at least the sign-in and checkout paths, use a synthetic transaction check (actually POST a test request, look for a real success response body), not just a ping-for-200. Store the test-account credentials in the monitor's secret store. 3. Set frequency (every one to five minutes for critical paths) and set a location diversity option if the service offers it, so a single-region outage on their side doesn't page me. 4. Configure notifications sensibly: alert only after two consecutive failures to avoid pager fatigue from a single blip. Route notifications to a channel that actually wakes me up (SMS or a real pager, not email). 5. Wire the monitor status into a public or internal status page so I can point users at 'yes, we know' instead of answering ten identical support tickets. Don't monitor every endpoint; pick the five to ten that matter. The deliverable is the monitors configured, alert routing tested by triggering a fake failure, and a link to the status page (public or private).

What This Does / How This Helps

This puts real, off-server uptime checks on the routes users actually use, with sane alert thresholds and a status page, so outages become a page in minutes instead of a support ticket in hours. Self-monitoring is a trap. When the server goes down, its own health check goes with it, and the dashboard lies about being fine. External monitoring hits the app from outside and tells the truth. Watching the paths users care about (not just /) is how you catch the checkout-broken-but-homepage-fine class of outage that quietly kills conversions.

Want to skip doing this by hand?

Fortivibe audits your app for all of the areas these prompts cover (and more).

See What We Check

Related Prompts