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.
Senior DevOps Engineer with 8.5+ years of experience. Otherwise an avid artist, reader, cinephile & football fan. Looking forward to connecting with everyone :)
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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.
Having automated reports is nice, but of course they should be accompanied by hand written updates.
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.