DEV Community

Discussion on: What Status Page Provider or Project Do You Recommend?

Collapse
vinayhegde1990 profile image
Vinay Hegde • Edited on

Would your end goal be a Status page that's manually updated by someone every time an incident occurs & on resolution OR 1 that auto-monitors all your service endpoints & sends you alerts (Slack, Email, SMS, Webhooks) in case of failures?

Collapse
molly profile image
Molly Struve (she/her) Author

Definitely manual. We had a pretty robust alerting and monitoring system at my previous employer, Kenna, and even then I wouldn't trust it to set a status page. I also think a large part of the status page is explaining what is going on to users. I think that usually needs a human touch bc we can translate what is breaking into understandable terms for those experiencing problems.

Collapse
villelahdenvuo profile image
Ville Lahdenvuo

Having automated reports is nice, but of course they should be accompanied by hand written updates.

Collapse
vinayhegde1990 profile image
Vinay Hegde • Edited on

I agree about the human touch part to convey key information to users but then it's an overhead for the team that maintains the page since there could be gaps in the process.

On that note, I'd recommend Statping which is open source, easy to build & highly customisable that I deployed at my previous org, Bizongo providing a central dashboard for all internal users (tech/non-tech) to view availability in real-time.