fleet-debugger
fleet-debugger copied to clipboard
Synced local file(s) with [googlemaps/.github](https://github.com/googlemaps/.github). Changed files Synced local .github/workflows/dependabot.yml with remote .github/workflows/dependabot.yml --- This PR was created automatically by the [repo-file-sync-action](https://github.com/BetaHuhn/repo-file-sync-action) workflow run [#9064278934](https://github.com/googlemaps/.github/actions/runs/9064278934)
Switch all collect endpoints to `collectCalls` rather than `collectCalls`
## :rotating_light: The automated release from the `main` branch failed. :rotating_light: I recommend you give this issue a high priority, so other packages depending on you can benefit from your...
This attemps to get sample bigquery queries into a more easily consumed form than our documentation. For now, the set of queries is sources from my somewhat unstructured explorations. Once...
Now that fleet-debugger is reading from bigquery it should be straightforward to start exposing some sample queries that look at the entire fleet, instead of just a single vehicle.
Right now it's not obvious w/o deeply inspecting the jsonpayload that a given operation actually failed.
W/o actual routes in cloud logging we can't compute route deviations ... but we can show when nav sdk thinks the user is off route. Unclear how the OFFROUTE nav...
Actual pickup/dropoff points are redacted from the logs. Can infer locations by the nearest (in time) update vehicle call to the trip status change.
Add a toggle button that will show all the generated routes for a vehicle. Ideally compute a 'deviation score' based on actual route driven vs initial guided route.
fleet-debugger currently focuses on UpdateVehicle and ignores the GetVehicle/trip/task calls. We've been getting bug reports about what the JSJS or consumer SDK sees. we should be able to visualize the...