Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Provide a status page #134

Open
geektoor opened this issue Jul 29, 2020 · 4 comments
Open

Provide a status page #134

geektoor opened this issue Jul 29, 2020 · 4 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request mirrored-to-jira This item is also tracked internally in JIRA

Comments

@geektoor
Copy link

geektoor commented Jul 29, 2020

Feature description

As we already saw that communication is a bit complicated, especially when it comes to users you don't know that they're your users, it would be worth to provide a status page about the services. A suggestion would be to take the most important parts and "monitor" them. It must be automated long term, but even a way to notify users (public services like statuspage.io allow users to subscribe to updates) would be a step forward to improve trust.
My proposal for the services that should be covered in a first step:

  • Website
  • iOS App
  • Android App
  • Endpoint(s)
  • Hotlines

Problem and motivation

As there is no link between the app and the users (and there must/should not), and most users are most likely not to technical, a simple status overview about the CWA Services could help them to get aware of issues. Status pages are implemented by many big companies and help to identify issues, even if the users are not too technical. Additionally as its mostly providing a history about the services reliability, it also improves the reputation and trust.

Is this something you're interested in working on

No


Internal Tracking ID: EXPOSUREAPP-2038

@ghost
Copy link

ghost commented Jul 29, 2020

@geektoor thanks for bringing this up. Regarding that, we are already in discussion internally, but have no final concept yet-

Best regards,
LMM
Corona Warn-App Open Source Team

@ghost ghost transferred this issue from corona-warn-app/cwa-website Jul 29, 2020
@ghost ghost added documentation Improvements or additions to documentation enhancement New feature or request labels Jul 29, 2020
@ghost ghost assigned MarisaWollner Aug 6, 2020
@ghost ghost added the mirrored-to-jira This item is also tracked internally in JIRA label Aug 6, 2020
@ghost ghost assigned hermesmar Sep 22, 2020
@sapcoder123 sapcoder123 assigned maugst and unassigned JoachimFritsch Dec 18, 2020
@rugk
Copy link

rugk commented Apr 23, 2021

For detecting issues/random failures of checks (and finding out whether that was a server issue), I agree a monitoring/status page – even if it is just some green or well… red… circles – would be nice. See corona-warn-app/cwa-app-android#2941

@achisto
Copy link

achisto commented Jan 24, 2022

There's another incident, where a public status page could have been and still could be of some help: corona-warn-app/cwa-quicktest-onboarding#83

There are more and more services connected to CWA, starting with the hotlines through to everything around the server infrastructure and newer services like the Schnelltestportal. Currently, in the case of an incident there is no easy way to get an overview about affected services and mitigation possibilities on the user-side.

Is there any update on the internal discussions, that started in July 2020?

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Jan 27, 2022

I started two status pages:

I can't guarantee that they detect all outages/issues, they are more like an indicator.

A good status page where the shown status is guaranteed to be correct can only be provided by the project team.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation enhancement New feature or request mirrored-to-jira This item is also tracked internally in JIRA
Projects
None yet
Development

No branches or pull requests

8 participants