Fleet CAN Remote Monitoring Dashboard

I’m building a web-based dashboard that taps directly into each truck’s CAN bus so our technicians can see what the vehicle is doing without ever touching it. The core of the project is already underway—I’m mapping proprietary CAN IDs—but I need help turning the raw stream into a clear, actionable interface.

What the finished tool must do
• Display all trucks in real time, refreshing the view as soon as fresh CAN data arrives.
• Raise predictive maintenance alerts before a part fails, based on patterns we derive from the ongoing feed.
• Let a technician drill into any vehicle and start remote troubleshooting immediately.

Visual layout
For now, everything should be presented in a single table. Each row represents one truck and the table must surface its active Diagnostic Trouble Codes alongside key timestamps and status flags. We can add charts or maps later, but the initial focus is clean tabular data that loads fast and filters smoothly. This needs to have the potential to scale to 10,000 trucks.

Data flow & tech stack
You’ll connect to a message broker that I already use for the CAN frames; from there, transform the payloads, resolve the proprietary IDs, and populate the front end. I’m language-agnostic as long as it’s solid and maintainable—Node.js with Socket.io, Python with FastAPI, or a Go service are all fine. On the front end, React or Vue are preferred so we get snappy table interactions.

Acceptance criteria
1. Live table updates within two seconds of the CAN frame arriving.
2. Columns for truck ID, timestamp, DTC number, severity, and an expandable details pane.
3. Alert logic that flags a row when thresholds we set together are crossed.
4. Clean, documented code plus a Docker-compose file so I can spin up the whole stack on my end.

If you’ve built telemetry, fleet, or CAN-bus tools before, this should feel familiar. Let’s get this diagnostics view online so we can keep our trucks rolling.