Before you build a dashboard or chase a number that looks wrong, you need to know one thing: what data are your units sending? A chart can only show what Wialon has. The Events view is where you check that — a per-vehicle overview of exactly which data each unit in your fleet is sharing.
It is less a report than a technical read on your fleet’s data. You look at it first, before you build anything on top.
One row per vehicle, grouped by data type
Each unit is a row, and the columns are grouped by the kind of data Wialon reports:
- Mileage — distance, trips, and drive time.
- Speeding — speed events and their duration.
- Fuel — consumption, fillings, and drains from LLS sensors. Worth checking before you trust a fleet total: see reading Wialon fuel reports.
- Ignition — engine cycles and hours.
- Sensors — your custom sensors and counters.
- Eco-driving — violations, broken down by criterion.
Every cell is a value for the date range you choose. A vehicle that reports nothing for a category shows a dash, so the gaps are as visible as the data — and each unit carries a plain Data / No Data marker so you can tell at a glance which vehicles are reporting at all.
See what each unit shares
This is the point of the view. The category groups for ignition, sensors, and eco-driving only appear when a unit returns that data, and any metric a unit is not sending is left blank rather than faked with a zero. So the table is an honest map of your fleet’s coverage: which units report fuel, which expose a custom counter, which send eco-driving criteria, and which are quietly sending nothing.
That makes it the first stop for two jobs:
- Before building a dashboard — confirm the data you want to chart is there. If a unit does not report fuel here, a fuel widget will be empty too.
- When troubleshooting — an empty chart or a vehicle missing from a report usually traces back to here. The dash in the Events table tells you the unit is not sending that detector, so you fix it at the source in Wialon instead of guessing. It is the same distinction the API makes when it answers error 1001, no messages for the selected interval — an empty answer is data, not a failure.
The Events view reads the same Wialon event data the dashboard does, so what you see here is exactly what is available to build on. Once you know what a unit shares, you can put it on a custom Wialon dashboard.
Sort, reorder, and focus
The table bends to the question you are asking. Sort by any column to bring the worst-reporting units to the top, drag columns into the order you want, resize them, and show or hide whole category groups to cut the table down to what matters. Pick the units and the date range, and the coverage is recalculated for that period.
Found a gap in your data?
If there is a metric, a sensor, or a coverage check you want in the Events view, send us a note and we will build it together.
