Feature: Auto-Config Wizard for Quick Monitor Setup

Summary

Add a \"Quick Setup Wizard\" / \"Auto Config\" feature that allows new customers to rapidly configure multiple monitors for a website or service with a single URL input and one-click enablement.

Problem

New customers, especially less technical ones, face friction when setting up comprehensive monitoring. They may not know which monitor types are important or what reasonable defaults look like. This leads to:

• Incomplete monitoring coverage
• Slower time-to-value
• Potential churn from setup complexity

Proposed Solution

Core Flow

1. User enters a URL (e.g., www.example.com)
2. System analyzes the target and generates a recommended monitor set
3. User sees a checklist with toggles, tooltips explaining each monitor's purpose
4. User enables desired monitors (with "Enable all recommended" option)
5. Monitors are created with sensible defaults

Monitor Types for Website Template

| Monitor | Purpose | Default Interval |
|---------|---------|------------------|
| HTTP Check | Up/down availability | 5 min |
| HTTP Content Check | Detect unexpected content changes | 1 hour |
| DNS Check | Name resolution monitoring | 15 min |
| Domain Expiry Watch | Alert before registration lapses | Daily |
| ICMP/Ping | Underlying host availability | 5 min |
| TCP Port (80/443) | Port-level health separate from HTTP | 5 min |
| SSL Certificate Expiry | Alert before cert expires | Daily |

Discovery Phase (Optional Enhancement)

Before presenting the checklist, probe the target to auto-detect:

• HTTPS availability (check port 443)
• Open ports (common web ports)
• Load balancing (multiple A records)
• Presence of robots.txt/sitemap

Template Expansion (Future)

Extend to other use cases:

• API Endpoint: HTTP + latency tracking + SSL cert expiry
• Mail Server: SMTP check, IMAP check, MX records, SPF/DKIM validation
• Database Server: TCP port check + custom health endpoint
• Generic Server: ICMP + SSH port + custom TCP ports

UX Considerations

• Clear tooltips explaining what each monitor does and why it matters
• Show estimated quota/cost impact per monitor
• Allow editing defaults before creation
• "Advanced" expansion for power users to tweak intervals/thresholds

Technical Notes

• Need URL/domain parsing to extract registrable domain for WHOIS checks
• Content check should ignore dynamic elements (timestamps, session IDs, ads)
• Consider rate limiting the discovery probes

Labels

enhancement, onboarding, ux