Fleet Debugger Tool

A debugging tool for use with the stateful Last Mile Fleet Solutions and On Demand Rides and Deliveries solutions. Fleet debugger does not yet directly support the Google Navigation SDK users must integrate with the Trip and Order Progress SDKs.

Disclaimer

This is not an officially supported Google product

Demos

• Demo with GPS accurracy issues
• Demo with multiple trips
• Demo with LMFS tasks

Getting Started

Dependencies

Download & install node Download & install gcloud

Setup authentication

gcloud config set project <your project id>
gcloud auth login
gcloud auth application-default login

Populate ./node_modules directory

npm install

Examples

View historical data from my-vehicle-id via Trip and Order Progress SDKs

# Generate data files
dune-buggy.js historical --apikey <your api key> --vehicle=my-vehicle-id
# start UI (should open up browser to localhost:3000
npm start

Generate sharable artifact

# Generate data files
dune-buggy.js historical --apikey <your api key> --vehicle=my-vehicle-id
# build sharable, static artifact.  Any webserver should be able to host this.
npm run build
tar -czf support-dump.tgz build

Generating a support bundle

See Reporting Issues for details on how to generate a support bundle that can be used when reporting bugs or other issues to google.

Key Features

Filter & Inspect log messages

Customize which fields are shown in table view

View important status changes: vehicle status, trip status, navigation status

View raw GPS information, including location, accuracy & heading

Comprehensive, Pre-built Visualizations

• Visualize multiple trips for one vehicle
• Replay Vehicle Movement
• GPS Accuracy
• Vehicle Speed
• Vehicle Heading
• Dwell Times

Extensibility

• Easily add aditional related data from cloud logging

Running On Windows

Fleet debugger has been verified to run on Windows 10 in the command shell. git, node and gcloud need to be installed first.

Example

node dune-buggy.js historical --apikey <your api key> --vehicle=my-vehicle-id
# address line ending format issues
npm run format 
npm start