Test vehicle-positions.pb

[owades]

We need to create regular tests to run on our vehicle-positions RT feed to ensure they're working as expected. Create logic to check each live agency's RT feed every X minutes, and report on the results. We should be able to compare this report in some way with the nightly GRaaS report.

1. Set up the gtfs-realtime-bindings python classes. 2. Create a script that checks the PB and reports a summary of what it sees (# agencies, # vehicles per agency)
2. Create logic that runs the above script once per X minutes, and logs the results. This should likely be another google datastore entity.
3. Create a way to summarize the results.

[unreasonableman]

@owades I would suggest the following (some of this was discussed in our triage meeting today):

• the pb test script runs on an "always-on" machine, like a raspberry pi
• the script connects to the position-update feed for each onboarded agency and logs how many vehicles are present in the feed at that time. Logs are kept local
• once a day, the script sends an update to the DB. The update could be a JSON array with an element for each agency that lists:
  • total number of vehicles present in the agency's feed that day. This could include both a "raw" update count that just says how many vehicle records were present, and a unique vehicle count that shows how many distinct vehicles were tracked
  • minimum, average and maximum number of vehicles present in an update

That is probably enough for the MVP. We can get fancier later with keeping track of consecutive updates show a particular vehicle, etc.

[evansiroky]

Hello GRaaS team. The data-services team is working on building out a GTFS-RT data consumption pipeline. Is this something that could be used here in a similar way as was done with cal-itp/data-infra#997?

[owades]

Thanks @evansiroky, we're absolutely interested. What would be a good way to stay in the loop and/or make our needs known?

[evansiroky]

Right now, we're working on a number of items, but the one issue that y'all would probably be most interested in is that we're planning on running all RT feeds that get downloaded through the gtfs-realtime-validator tool to check for errors. It's a decent lift, but we're tracking the buildout of the pipeline in cal-itp/data-infra#1009 and then having the ability to analyze in metabase which is tracked in cal-itp/data-infra#570.

[unreasonableman]

Checking for errors is an important aspect, but we're also very interested in tracking stats such as overall volume of position updates, number of tracked vehicles per day, etc.

…

On Wed, Feb 23, 2022 at 10:13 AM Evan Siroky ***@***.***> wrote: Right now, we're working on a number of items, but the one issue that y'all would probably be most interested in is that we're planning on running all RT feeds that get downloaded through the gtfs-realtime-validator <https://github.com/MobilityData/gtfs-realtime-validator> tool to check for errors. It's a decent lift, but we're tracking the buildout of the pipeline in cal-itp/data-infra#1009 <cal-itp/data-infra#1009> and then having the ability to analyze in metabase which is tracked in cal-itp/data-infra#570 <cal-itp/data-infra#570>. — Reply to this email directly, view it on GitHub <#107 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGLQDNNTA23ONS3OLCVFT3U4UPUXANCNFSM5PCSHVJQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[evansiroky]

Checking for errors is an important aspect, but we're also very interested in tracking stats such as overall volume of position updates, number of tracked vehicles per day, etc.

Actually, we could probably answer those questions with our existing infrastructure since we have a pipeline built out for the vehicle positions in particular. We would just need to add the GRaaS feeds to the https://github.com/cal-itp/data-infra/blob/main/airflow/data/agencies.yml file to begin consuming that data. If we're looking to match that with information from the static feed, that might be a little more effort

[unreasonableman]

sweet!

…

On Wed, Feb 23, 2022 at 12:08 PM Evan Siroky ***@***.***> wrote: Checking for errors is an important aspect, but we're also very interested in tracking stats such as overall volume of position updates, number of tracked vehicles per day, etc. Actually, we could probably answer those questions with our existing infrastructure since we have a pipeline built out for the vehicle positions in particular. We would just need to add the GRaaS feeds to the https://github.com/cal-itp/data-infra/blob/main/airflow/data/agencies.yml file to begin consuming that data. If we're looking to match that with information from the static feed, that might be a little more effort — Reply to this email directly, view it on GitHub <#107 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGLQDILUY3CICBOEVF6JEDU4U5E7ANCNFSM5PCSHVJQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>