Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An endpoint to fetch the system status is needed #411

Open
Bertware opened this issue Jul 4, 2020 · 0 comments
Open

An endpoint to fetch the system status is needed #411

Bertware opened this issue Jul 4, 2020 · 0 comments

Comments

@Bertware
Copy link
Member

Bertware commented Jul 4, 2020

At this moment, the NMBS servers are struggling. This means that neither the official app nor iRail can provide any travel information. While many apps can benefit from their own status feed for an in-app banner or notification (that also can handle app update notifications in case of a botched release or an app <-> iRail issue that isn't a problem on iRail's side), these "app-specific" feeds need to be able to fetch the iRail/NMBS status automatically. A status endpoint could contain one status object for each endpoint, where each status object contains a status enum and an error message in Dutch, French, German and English. The error message should only be used in case the endpoint is unhealthy.

  • The status can be fetched from uptimeRobot (status.irail.be)
  • To prevent incorrect warnings, the used tests should be down for at least a minute before marking an endpoint as unhealthy.
  • To prevent incorrect "up-again!" data, the used tests should be up for at least two minutes before marking an endpoint as recovering. During the recovering period, the endpoint is usable, but might go down again, or might fail random requests.
  • An endpoint can be marked as healthy after 15 minutes.
  • Optionally, the down time or datetime when the endpoint went offline can be included
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant