Basically I had a similar problem to Harsh Shandilya. To keep things simple I wanted a static status page but couldn't find anything without having to manually add incidents/change component statuses and redeploy etc.
I ended up making my own called Issue Status, it's a static status page built using React and GitHub Issues which it uses for component and incident reporting.
For automating there's lots of options, you'll need some sort of monitoring tool, I've tested using New Relic and Uptime Robot (you could also use Pingdom or similar) and then use Zapier (RSS Feed or New Relic trigger) with the GitHub integration. You can also use the GitHub API directly to update the status page.
French web developer mainly but touches everything. Volunteer mod here at DEV. I learn Nuxt at this moment and databases. — Addict to Cappuccino and Music
Basically I had a similar problem to Harsh Shandilya. To keep things simple I wanted a static status page but couldn't find anything without having to manually add incidents/change component statuses and redeploy etc.
I ended up making my own called Issue Status, it's a static status page built using React and GitHub Issues which it uses for component and incident reporting.
For automating there's lots of options, you'll need some sort of monitoring tool, I've tested using New Relic and Uptime Robot (you could also use Pingdom or similar) and then use Zapier (RSS Feed or New Relic trigger) with the GitHub integration. You can also use the GitHub API directly to update the status page.
Demo: tadhglewis.github.io/issue-status
Source: github.com/tadhglewis/issue-status
My status page: status.tadhglewis.com
Great!