Zero to Monitored: Setting Up UptimeGuard in 15 Minutes
A quick-start walkthrough for getting your first monitors, alerts, and status page running with UptimeGuard. From signup to fully monitored in 15 minutes flat.
Zero to Monitored: Setting Up UptimeGuard in 15 Minutes
You've decided to monitor your site. Great. Let's get you set up fast.
This guide takes you from zero to a fully monitored website with alerts and a status page in 15 minutes.
Minute 0-2: Sign Up and Log In
- Visit UptimeGuard and create your account
- Verify your email
- You're in the dashboard
Minute 2-5: Add Your First Monitors
Your Website
- Click "Add Monitor"
- Type: HTTP(S)
- URL: your-website.com
- Check interval: 30 seconds
- Regions: Select at least 3 (US, Europe, Asia)
- Keyword: Add your brand name (catches content errors, not just HTTP errors)
Your API (If Applicable)
- Add another monitor for your API endpoint
- Type: HTTP(S)
- URL: api.your-website.com/health
- Check interval: 30 seconds
Your SSL Certificate
- Add an SSL monitor for each domain
- Alert threshold: 30 days before expiry
Minute 5-8: Configure Alerts
Slack Integration
- Go to Alert Channels → Add Slack
- Authorize the connection
- Select your preferred channel
Email Alerts
- Add your email address
- Add your team members' emails
SMS (For Critical Alerts)
- Add your phone number
- Verify via the confirmation code
Set Alert Rules
- Website down → Slack + SMS
- API down → Slack + SMS
- SSL expiring → Email
- Response time degraded → Slack only
Minute 8-11: Create Your Status Page
- Go to Status Pages → Create
- Add a custom subdomain (status.your-website.com)
- Add your monitored services as components
- Customize the branding (logo, colors)
- Publish
Your customers can now check your system status anytime.
Minute 11-14: Add Team Members
- Go to Team → Invite Members
- Add your team's email addresses
- Assign roles (Admin, Member, Viewer)
- They'll receive invitations to join
Minute 14-15: Verify Everything Works
- Check your dashboard — all monitors should show "Up"
- Click "Send Test Alert" to verify each channel
- Visit your status page to confirm it's live
- Share the status page URL with your team
What You Just Set Up
In 15 minutes, you now have:
- ✅ 30-second monitoring on your website and API
- ✅ SSL certificate expiry monitoring
- ✅ Multi-region checking from 3+ locations
- ✅ Slack, email, and SMS alerting
- ✅ A public status page for customers
- ✅ Team access for your colleagues
Next Steps (When You Have Time)
- Add monitors for your database (port check)
- Set up heartbeat monitoring for cron jobs
- Configure on-call rotation
- Add keyword checks for critical pages
- Integrate with PagerDuty for escalation
You're monitored. Your site, your API, and your SSL certificate are all being watched 24/7 from multiple global locations. If anything goes wrong, you'll know in seconds.
Now go build features. We'll watch the infrastructure.
Written by
UptimeGuard Team
Related articles
Cron Job Monitoring: How to Know When Your Scheduled Tasks Fail
Cron jobs fail silently. Backups don't run, reports don't send, data doesn't sync — and nobody notices for days. Here's how heartbeat monitoring fixes that.
Read morePort Monitoring Explained: Protect Your Databases, Mail Servers, and More
Not everything runs on HTTP. Your databases, mail servers, and custom services need monitoring too. Port monitoring catches failures that web checks can't.
Read moreChoosing the Right Check Interval: 30 Seconds vs 5 Minutes Matters More Than You Think
The difference between checking every 30 seconds and every 5 minutes is the difference between catching an outage in under a minute and missing it for up to 10 minutes.
Read more