From daba01d259b060ad0d3f3f2c21c7b98438d122d2 Mon Sep 17 00:00:00 2001 From: Martyn Welch <martyn.welch@collabora.com> Date: Tue, 16 Mar 2021 11:11:30 +0000 Subject: [PATCH] Minor updates to Status Page Review document - Minor spelling corrections - Remove "docs" service as it's not longer available Signed-off-by: Martyn Welch <martyn.welch@collabora.com> --- content/concepts/status-page-review.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/content/concepts/status-page-review.md b/content/concepts/status-page-review.md index 83d73ab84..638e8fc4c 100644 --- a/content/concepts/status-page-review.md +++ b/content/concepts/status-page-review.md @@ -97,7 +97,7 @@ following options have been found: As there are an abundance of tools and services available which provide status page functionality, choosing from these existing solutions will be preferred over a home grown solution, assuming that one can be found to fit our -requirements, with a home grown solution only concidered if none of the +requirements, with a home grown solution only considered if none of the existing solutions are appropriate. Our approach is to: - Determine services that need to be monitored, this will be critical to @@ -143,9 +143,6 @@ update/extend existing apt based installations. - **hawkBit**: This is a deployment management system that is being integrated into Apertis. It provides both a web UI and rest API. Both of these should be monitored. -- **docs**: This holds the generated documentation for some packages. It is not - as important as some of the other pages, but wouldn't necessarily get noticed - quickly if it wasn't working. Whilst this list could arguably be reduced a little to just target core services, it would be prudent to choose a service that would allow Apertis room @@ -180,7 +177,7 @@ later criterion, hence the lack of answers on less suitable options. # Recommendation -Based on the above evalution, the top 4 options would appear to be: +Based on the above evaluation, the top 4 options would appear to be: - Better Uptime - Gatus @@ -192,13 +189,13 @@ self-hosted solution. A self-hosted solution has the advantage that it will remain available long-term, not being reliant on an outside provider, however they will also -require mantenance and up keep. A externally provided service has the advantage +require maintenance and up keep. An externally provided service has the advantage that it is hosted on distinct infrastructure from that hosting the other Apertis services and thus less likely to be made unavailable by a fault affecting the whole platform. An external service is also likely to provide a more independent and reliable evaluation of the platform status. -Based on this our recommendation would be to utilise UptimeRobot to provide a +Based on this our recommendation would be to utilize UptimeRobot to provide a status page for Apertis. # Risks -- GitLab