As part of MobiData-BW (DE-BW's transport data aggregator), we continuously monitor two GTFS feeds' data quality but running the GTFS Validator on it. We want to be able to see changes & trends over time, and given that we're using Prometheus & Grafana to monitor many other things, I built a quick-and-dirty adapter.
However, now that gtfs-validator-api exists, its sole "unique selling point" is converting the validator's output into the Prometheus metrics text format. Ideally, we'd be able to consume validation results as Prometheus/OpenTelemetry metrics directly from gtfs-validator-api, and deprecate our gtfs-validator-metrics-service.
What do you think?
As part of MobiData-BW (
DE-BW's transport data aggregator), we continuously monitor two GTFS feeds' data quality but running the GTFS Validator on it. We want to be able to see changes & trends over time, and given that we're using Prometheus & Grafana to monitor many other things, I built a quick-and-dirty adapter.However, now that
gtfs-validator-apiexists, its sole "unique selling point" is converting the validator's output into the Prometheus metrics text format. Ideally, we'd be able to consume validation results as Prometheus/OpenTelemetry metrics directly fromgtfs-validator-api, and deprecate ourgtfs-validator-metrics-service.What do you think?