![]() It wasn't my first foray in status page design. ![]() In the end, a manually curated dashboard provides important usability benefits over an automated system, and all major organisations have one. Worse, they also tend to generate false positives, and don't clearly show users which issues are critical. But those are hard to understand for users. We already have two monitoring tools in the sysadmin team: Icinga (a fork of Nagios) and Prometheus, with Grafana dashboards. ![]() The latter is still on the sysadmin roadmap, but a status page seemed like a good solution for the former. I surveyed internal users at the end of 2020 to see what could be improved, and one of the suggestions that came up was to "document downtimes of one hour or longer" and generally improve communications around monitoring. The first step in setting up a service page was to realize we needed one in the first place. This post documents why we launched, how the service was built, and how it works. The status page also displays outages related to Tor internal services, like our GitLab instance. You can check status.torproject for news about major outages in Tor services, including v3 and v2 onion services, directory authorities, our website ( ), and the tool. The Tor Project now has a status page which shows the state of our major services.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |