Open isabelle-dr opened 2 years ago
Relevant Best Practice:
The URL should be directly accessible without requiring a login to access the feed. If desired, API keys may be used but registration for API keys should be automated and available to all.
Issue by barbeau May 10, 2017 Originally opened as https://github.com/CUTR-at-USF/gtfs-realtime-validator/issues/278
Summary:
Currently, if the GTFS-rt server does not respond with a valid message, we don't show any indication in the GUI and we log something like this to output:
or:
We should log this as an error so it's visible in the log. We may also want to surface this in the GUI in the HTTP metrics section as "HTTP failures".
Steps to reproduce:
Monitor a feed that results in HTTP failures
Expected behavior:
Log failures as errors, perhaps show them in HTTP metrics section
Observed behavior:
No indication of failures are shown in the log or HTTP metrics in GUI