Fleet IoT Sensor Anomaly Logs

This dataset provides detailed logs of anomalies detected by IoT sensors across fleet vehicles, including sensor readings, anomaly types, severity, geolocation, and resolution status. It supports predictive maintenance, asset security, and operational analytics for transportation startups, enabling rapid integration with anomaly detection models and edge computing frameworks.

  • last updated 8 Dec 2025
  • by GoMask
The brief that made it

Predictive maintenance and failure prevention for fleet vehicles

Sample rows

preview · 8 of 120 rows · all 17 columns
log_idstringsensor_typestringexpected_value_range_minfloatresolvedbooleananomaly_typestringvehicle_idstringsensor_idstringanomaly_severityintegersensor_valuefloatexpected_value_range_maxfloattimestampdatetimelocation_latitudefloatlocation_longitudefloatvehicle_statusstringresolution_timestampdatetimeanomaly_descriptionstringresolution_notesstring
LOG-001temperature10truethreshold_breachVEH-1001SEN-temperature-014180.51202024-06-01T10:23:00Z37.7749-122.4194moving2024-06-01T11:02:00ZEngine temperature exceeded critical threshold during midday city route.Vehicle stopped and engine cooled. Sensor recalibrated, driver notified.
LOG-002gpsblankfalsemissing_dataVEH-1002SEN-gps-022blankblank2024-06-02T14:15:00Z40.7128-74.006idleblankGPS signal lost for over 10 minutes on rural highway segment.blank
LOG-003fuel20trueoutlierVEH-1003SEN-fuel-01242.1402024-06-03T09:32:00Z34.0522-118.2437moving2024-06-03T10:00:00ZSudden spike in fuel consumption detected during morning delivery.Driver advised to check for fuel leaks. No issue found, log closed.
LOG-004vibration2falseunexpected_patternVEH-1004SEN-vibration-03312.592024-06-03T16:41:00Z51.5074-0.1278movingblankIrregular vibration pattern detected during acceleration phase.blank
LOG-005pressure28truethreshold_breachVEH-1005SEN-pressure-01314362024-06-04T06:12:00Z35.6895139.6917maintenance2024-06-04T06:51:00ZTire pressure dropped below safe level before scheduled departure.Tire replaced and pressure reset. Vehicle cleared for operation.
LOG-006humidity30truethreshold_breachVEH-1006SEN-humidity-02499.9852024-06-05T12:06:00Z48.85662.3522moving2024-06-05T12:50:00ZHumidity sensor recorded levels above 99% after heavy rainfall event.Sensor replaced. Water ingress checked, no further anomalies detected.
LOG-007otherblanktrueotherVEH-1007SEN-other-042blankblank2024-06-06T15:13:00Zblankblankmaintenance2024-06-06T16:00:00ZFirmware error detected on custom sensor during diagnostics.Firmware updated and sensor restarted. Issue resolved.
LOG-008gpsblankfalseunexpected_patternVEH-1008SEN-gps-032blankblank2024-06-07T08:45:00Z60.169924.9384movingblankGPS drift detected during navigation in remote area.blank

What the 120 rows show

from the 120-row sample

Vibration (sensor type) stands out: mean expected_value_range_min is 1.9, against 23.5 for the rest.

  • 57%resolved = true
  • 20.0median expected_value_range_min
  • 5vehicle statuses
  • 2.5median anomaly_severity
  • 19.3median sensor_value
  • 55.0median expected_value_range_max
Mean expected_value_range_min by sensor_type85 rows
0204013.2temper…19 rows1.9vibrat…18 rows28.8fuel13 rows28.9pressu…18 rows25.3humidi…17 rows
expected_value_range_min85 rows, in bands of 5
01020180116102018202040expected_value_range_min →

Median 20.0, from 1.0 to 40.0.

anomaly_type120 rows · 6 values
  1. threshold_breach45
  2. outlier27
  3. missing_data14
  4. unexpected_pattern13
  5. other13
  6. communication_error8
17 columns by typefrom the column list below
  • string 8
  • integer 1
  • float 5
  • datetime 2
  • boolean 1

Columns

17 columns in four groups
blueprint · 17 columns
columntypedescriptionexample
Text 8 columns
log_idstringUnique identifier for each anomaly log entryuniqueLOG-001
vehicle_idstringUnique identifier for the vehicle in the fleetVEH-1001
sensor_idstringUnique identifier for the IoT sensor reporting the anomalySEN-temperature-01
sensor_typestringType of sensor (e.g., temperature, vibration, GPS, fuel)7 valuestemperature
anomaly_typestringCategory of anomaly detected (e.g., outlier, threshold breach, missing data)6 valuesthreshold_breach
anomaly_descriptionstringDetailed description of the anomaly eventoptionalEngine temperature exceed…
vehicle_statusstringOperational status of the vehicle at anomaly time (e.g., moving, idle, maintenance)moving · idle · maintenance · offline · other · optionalmoving
resolution_notesstringNotes or actions taken to resolve the anomalyoptionalVehicle stopped and engin…
Numbers 6 columns
anomaly_severityintegerSeverity level of the anomaly (1=Low, 2=Medium, 3=High, 4=Critical)1 to 44
sensor_valuefloatSensor reading at the time of anomalyoptional180.5
expected_value_range_minfloatMinimum expected value for the sensor under normal conditionsoptional10
expected_value_range_maxfloatMaximum expected value for the sensor under normal conditionsoptional120
location_latitudefloatLatitude coordinate of the vehicle at anomaly detection-90 to 90 · optional37.7749
location_longitudefloatLongitude coordinate of the vehicle at anomaly detection-180 to 180 · optional-122.4194
Dates and times 2 columns
timestampdatetimeDate and time when the anomaly was detected2024-06-01T10:23:00Z
resolution_timestampdatetimeDate and time when the anomaly was resolvedoptional2024-06-01T11:02:00Z
True or false 1 column
resolvedbooleanIndicates whether the anomaly has been resolvedtrue

Use it for

  • resolved57%68 of 120 rowsmean expected value r…13.2temp…1.9vibr…28.8fuel28.9pres…

    A transportation dashboard

    The resolved rate, expected_value_range_min by sensor_type and a breakdown of anomaly_type. Excel, Power BI or Tableau.

  • Why do the 18 vibration rows have a mean expected_value_range_min of 1.9?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable logs with vehicle_id, sensor_id and sensor_type to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 17 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset120 rows17 columns
Yours1,000 rows17 columnslocation_latitude: UK only

blueprint · fleet-iot-sensor-anomaly-logs

Behind this dataset

Same schema. As many rows as you need.

These 120 rows came out of a blueprint — 17 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Each row represents a unique sensor event from a fleet vehicle.
  • Event types must include both operational and environmental anomalies.
  • Timestamp and vehicle ID are required for every entry.
  • Anomaly severity is categorized as low, medium, or high.
  • Sensor types must include GPS, temperature, and accelerometer.
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
fleet-iot-sensor-anomaly-logs

What should your data show?

Preview 20 rows free
No signup. No card.