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.

Sign up for GitHub

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

Jump to bottom

v6.db.transport.rest API status page inconsistent with my test results #33

Open
LilaHexe0 opened this issue Dec 17, 2024 · 1 comment
Open

v6.db.transport.rest API status page inconsistent with my test results #33

LilaHexe0 opened this issue Dec 17, 2024 · 1 comment

Comments

@LilaHexe0
Copy link

The API status page (https://stats.uptimerobot.com/57wNLs39M/793274556) claims 100% uptime on days where my personal monitoring (datadog) indicates otherwise:

Screenshot 2024-12-17 at 15-09-45 Test on v6 db transport res Datadog

Most/all of the failures are caused by 503 errors.

How exactly does the UptimeRobot check if the service is operational?
@traines-source
Copy link
Member

I think the status page only indirectly, if at all, monitors whether HAFAS requests themselves are working. Maybe one could switch to monitoring the /health endpoint directly, of course entailing many more additional requests towards HAFAS.

The 503s you've been encountering are mostly due to errors on the HAFAS side, and it seems that the DB HAFAS mgate.exe endpoint will be shut off soon (see public-transport/hafas-client#331 and
schildbach/public-transport-enabler#610)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@traines-source @LilaHexe0