Provide some classification?

[schierlm]

Looking at all the opensource options, it looks to me that some projects are quite "orthogonal" to each other.

What is the source of status updates? (more than one can apply)

• Automated service monitoring
• Manually added outages
• Planned maintenance

Who is the audience of the website? (more than one can apply)

• Internal staff (e.g. only visible after login; no details about outages)
• External users (visible without login, showing information curated for end-users, maybe even possibility for end-users to create account and filter)

How are users notified?

• By looking at the page (duh! :) )
• RSS feed
• E-Mail subscriptions
• Social services (Slack etc.)

Background is that I was looking for a status page for external users who can view outage information and maintenance windows and are able to self-subscribe via both e-mail and RSS.

From the 29 entries listed in the "opensource* section, only 3 (staytus, cachet, darkpixel/statuspage) qualify (unless I missed one or two), and about 5 more can only be definitely ruled out after you installed and tested them yourself and/or looked at the demo page.

I am sure that the page still provides help to many people, but for me, who came from the point to search an alternative for cachet (discontinued) and staytus (slightly buggy as it sometimes does not update the service status when an incident is logged), it became a time hog with effectively no better option than I already knew.

If you like to have this kind of information, How would such information best be added? With icons after the entries? As a table? How to mark "unsure" entries? I am willing to fill in as much as I remember from my journey about the 29 opensource entries and provide a pull request.

[ivbeg]

Hi @schierlm ! The idea is great, but it requires a manual review of each public status page, service, and open-source product. If you have time to do that, it would be just great! It could be added as a number of tables at the end of README.md page.

I suggest creating a pull request with the additional file with the name "REVIEW.md" or something and if the markup will be ok, I could merge it into README.md or to add a link to this review in README.md beginning.

[schierlm]

For the open source products, I created such a table, which is available here. No pull request as it does not include the services and public pages. Probably those might need other criteria (e.g. pricing models).

Also, some cells still contain question marks, as I found no easy way to install/test them and it was not immediately clear from the documentation (or I just missed it).

If anyone else wants to do similar things or services or fill in question marks, feel free to fork my repo and send the pull request either to me or back upstream.

[haukebruno]

I have the same idea/question about the services ones.

My personal use-case is to know which Services provides "good" REST APIs.

If this makes sense to you, I could do the research and create PRs :)