[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4175: Provide basic monitoring of critical services

[Tahoe-LAFS]

#4175: Provide basic monitoring of critical services
------------------------------------+-----------------------
     Reporter:  btlogy              |      Owner:
         Type:  enhancement         |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:
Launchpad Bug:                      |
------------------------------------+-----------------------
Description changed by btlogy:

Old description:

> ==== Scope
> !AsIs: Some of the critical services powering the Tahoe-LAFS project
> (mainly this Trac instance) can become unavailable w/o any active member
> of the community being notified.
>
> In many occasion, the downtime has to be reported by people on IRC (or
> [https://github.com/tahoe-lafs/infrastructure/issues/46 elsewhere])
> before someone with the proper access can take action.
>
> !ToBe: Implement a basic monitoring solution tracking the availability of
> the critical services and allowing relevant people to be notified as soon
> as one of them is detected as unavailable.
>
> We are proposing to use [https://github.com/upptime/upptime Upptime] to
> achieve this, and the end result can already be seen
> [https://leastauthority.github.io/tahoe-upptime here].
>
> ==== Value
>
> - Contributors would be able to see past and ongoing downtime's.
> - Maintainers would be able to be notified to take corrective action
> earlier.
> - Statistics about the availability of the services will be publicly
> available and support future changes.
>
> ==== Requirements
>
> - Transfer the existing git repository (already provisioned with Upptime,
> CI and pages) from LeastAuthority to Tahoe-LAFS org. on GH.
> - Reconfigure owner/org name where needed.
>
> ==== Additional information
>
> This enhancement is a very nice to have for the execution of the
> MoveOffTrac project, in which it is planned to replace the issue
> tracking, wiki and web landing page solution, and hopefully improve their
> availability.
>
> - #4161

New description:

 ==== Scope
 !AsIs: Some of the critical services powering the Tahoe-LAFS project
 (mainly this Trac instance) can become unavailable w/o any active member
 of the community being notified.

 In many occasions, downtime have been reported by visitors reaching on IRC
 (or [https://github.com/tahoe-lafs/infrastructure/issues/46 elsewhere])
 asking if someone with the proper access could take action.

 !ToBe: Implement a basic monitoring solution tracking the availability of
 the critical services and allowing relevant people to be notified as soon
 as one of them is detected as unavailable.

 We are proposing to use [https://github.com/upptime/upptime Upptime] to
 achieve this, and the end result can already be seen
 [https://leastauthority.github.io/tahoe-upptime here].

 ==== Value

 - Contributors would be able to see past and ongoing downtime's.
 - Maintainers would be able to be notified to take corrective action
 earlier.
 - Statistics about the availability of the services will be publicly
 available and support future changes.

 ==== Requirements

 - Transfer the existing git repository (already provisioned with Upptime,
 CI and pages) from LeastAuthority to Tahoe-LAFS org. on GH.
 - Reconfigure owner/org name where needed.

 ==== Additional information

 This enhancement is a very nice to have for the execution of the
 MoveOffTrac project, in which it is planned to replace the issue tracking,
 wiki and web landing page solution, and hopefully improve their
 availability.

 - #4161

--

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4175#comment:2>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage