Introduction to Uptime Monitoring
I built SitePulse to help freelancers and small agencies monitor their clients' websites. One of the main challenges they face is ensuring their clients' sites are always available. This can be a daunting task, especially when dealing with multiple sites.
Handling Uptime Checks
SitePulse checks for uptime by sending requests to the site and expecting an answer within 10 seconds. If the site doesn't respond or returns an error status twice in a row, and checks from both Europe and Asia can't reach it, the site is considered down. However, if either region can still reach the site, no alert is sent. I also implemented 'page must contain' checks, which allow users to specify text that must be present on the page for it to be considered up.
Trade-offs and Limits
When building SitePulse, I had to make some trade-offs. For example, I chose not to implement SSL certificate expiry checks or SMS/phone-call alerts. I also had to limit the free plan to 5 sites, checks every 5 minutes, and 7 days of history. The Pro plan, which is not yet available for upgrade, will offer more features such as domain expiry warnings, client status pages, and monthly client reports.
Conclusion
Building SitePulse has been a learning experience, and I'm still working on improving it. If you're interested in trying it out, you can sign up for the free plan, which includes 5 sites, checks every 5 minutes, and 7 days of history, at https://sitepulse.buymazing.in.
Top comments (0)