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.
Sample rows
preview · 8 of 120 rows · all 17 columns| log_idstring | sensor_typestring | expected_value_range_minfloat | resolvedboolean | anomaly_typestring | vehicle_idstring | sensor_idstring | anomaly_severityinteger | sensor_valuefloat | expected_value_range_maxfloat | timestampdatetime | location_latitudefloat | location_longitudefloat | vehicle_statusstring | resolution_timestampdatetime | anomaly_descriptionstring | resolution_notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| LOG-001 | temperature | 10 | true | threshold_breach | VEH-1001 | SEN-temperature-01 | 4 | 180.5 | 120 | 2024-06-01T10:23:00Z | 37.7749 | -122.4194 | moving | 2024-06-01T11:02:00Z | Engine temperature exceeded critical threshold during midday city route. | Vehicle stopped and engine cooled. Sensor recalibrated, driver notified. |
| LOG-002 | gps | blank | false | missing_data | VEH-1002 | SEN-gps-02 | 2 | blank | blank | 2024-06-02T14:15:00Z | 40.7128 | -74.006 | idle | blank | GPS signal lost for over 10 minutes on rural highway segment. | blank |
| LOG-003 | fuel | 20 | true | outlier | VEH-1003 | SEN-fuel-01 | 2 | 42.1 | 40 | 2024-06-03T09:32:00Z | 34.0522 | -118.2437 | moving | 2024-06-03T10:00:00Z | Sudden spike in fuel consumption detected during morning delivery. | Driver advised to check for fuel leaks. No issue found, log closed. |
| LOG-004 | vibration | 2 | false | unexpected_pattern | VEH-1004 | SEN-vibration-03 | 3 | 12.5 | 9 | 2024-06-03T16:41:00Z | 51.5074 | -0.1278 | moving | blank | Irregular vibration pattern detected during acceleration phase. | blank |
| LOG-005 | pressure | 28 | true | threshold_breach | VEH-1005 | SEN-pressure-01 | 3 | 14 | 36 | 2024-06-04T06:12:00Z | 35.6895 | 139.6917 | maintenance | 2024-06-04T06:51:00Z | Tire pressure dropped below safe level before scheduled departure. | Tire replaced and pressure reset. Vehicle cleared for operation. |
| LOG-006 | humidity | 30 | true | threshold_breach | VEH-1006 | SEN-humidity-02 | 4 | 99.9 | 85 | 2024-06-05T12:06:00Z | 48.8566 | 2.3522 | moving | 2024-06-05T12:50:00Z | Humidity sensor recorded levels above 99% after heavy rainfall event. | Sensor replaced. Water ingress checked, no further anomalies detected. |
| LOG-007 | other | blank | true | other | VEH-1007 | SEN-other-04 | 2 | blank | blank | 2024-06-06T15:13:00Z | blank | blank | maintenance | 2024-06-06T16:00:00Z | Firmware error detected on custom sensor during diagnostics. | Firmware updated and sensor restarted. Issue resolved. |
| LOG-008 | gps | blank | false | unexpected_pattern | VEH-1008 | SEN-gps-03 | 2 | blank | blank | 2024-06-07T08:45:00Z | 60.1699 | 24.9384 | moving | blank | GPS drift detected during navigation in remote area. | blank |
| LOG-009 | temperature | 10 | true | outlier | VEH-1009 | SEN-temperature-02 | 1 | -5.2 | 80 | 2024-06-08T12:21:00Z | -33.8688 | 151.2093 | moving | 2024-06-08T12:51:00Z | Temperature sensor reported below freezing value during midday. | Sensor recalibrated. No operational impact detected. |
| LOG-010 | fuel | blank | false | missing_data | VEH-1010 | SEN-fuel-02 | 1 | blank | blank | 2024-06-09T14:03:00Z | 55.7558 | 37.6176 | idle | blank | Fuel sensor failed to transmit data during last route. | blank |
| LOG-011 | vibration | 2 | true | threshold_breach | VEH-1011 | SEN-vibration-01 | 3 | 10.1 | 9 | 2024-06-10T07:45:00Z | 41.8781 | -87.6298 | moving | 2024-06-10T08:19:00Z | Vibration amplitude exceeded safe threshold during acceleration. | Suspension checked and repaired. Vibration normalized. |
| LOG-012 | pressure | 28 | true | threshold_breach | VEH-1012 | SEN-pressure-02 | 4 | 0 | 36 | 2024-06-11T09:12:00Z | 19.4326 | -99.1332 | maintenance | 2024-06-11T09:41:00Z | Pressure sensor reported zero value during maintenance check. | Sensor replaced. System recalibrated for accurate readings. |
| LOG-013 | humidity | 30 | true | outlier | VEH-1013 | SEN-humidity-03 | 2 | 12.2 | 85 | 2024-06-12T06:55:00Z | 52.52 | 13.405 | idle | 2024-06-12T07:28:00Z | Humidity sensor recorded abnormal low value after overnight storage. | Sensor recalibrated. Humidity readings normalized. |
| LOG-014 | gps | blank | false | communication_error | VEH-1014 | SEN-gps-04 | 1 | blank | blank | 2024-06-13T19:09:00Z | blank | blank | offline | blank | GPS sensor failed to communicate with central server. | blank |
| LOG-015 | fuel | 30 | false | threshold_breach | VEH-1015 | SEN-fuel-03 | 2 | 5 | 70 | 2024-06-14T04:22:00Z | 40.4168 | -3.7038 | idle | blank | Fuel sensor reading below minimum expected level at start of shift. | blank |
| LOG-016 | vibration | 2 | true | outlier | VEH-1016 | SEN-vibration-02 | 3 | 6.5 | 4 | 2024-06-15T17:32:00Z | -23.5505 | -46.6333 | moving | 2024-06-15T18:10:00Z | Unusual vibration spike detected during heavy load operation. | Load distribution adjusted. Vibration normalized. |
| LOG-017 | pressure | 28 | false | other | VEH-1017 | SEN-pressure-03 | 3 | blank | 36 | 2024-06-16T11:23:00Z | 59.3293 | 18.0686 | maintenance | blank | Pressure sensor calibration error detected during scheduled check. | blank |
| LOG-018 | humidity | 20 | true | threshold_breach | VEH-1018 | SEN-humidity-01 | 4 | 100 | 85 | 2024-06-01T12:22:00Z | 43.6532 | -79.3832 | idle | 2024-06-01T13:00:00Z | Humidity sensor exceeded safe range while parked in humid environment. | Cabin dehumidified and sensor replaced. Vehicle returned to service. |
| LOG-019 | temperature | 30 | true | threshold_breach | VEH-1019 | SEN-temperature-03 | 3 | 130 | 120 | 2024-06-02T16:33:00Z | 35.6762 | 139.6503 | moving | 2024-06-02T17:15:00Z | Engine temperature briefly exceeded max limit during uphill climb. | Engine cooled at rest stop. Driver advised to monitor temperature. |
| LOG-020 | gps | blank | false | missing_data | VEH-1020 | SEN-gps-05 | 1 | blank | blank | 2024-06-03T18:46:00Z | 27.9878 | 86.925 | idle | blank | GPS data not received for 5 minutes in mountainous region. | blank |
What the 120 rows show
from the 120-row sampleVibration (sensor type) stands out: mean expected_
- 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
Median 20.0, from 1.0 to 40.0.
- string 8
- integer 1
- float 5
- datetime 2
- boolean 1
Columns
17 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 8 columns | |||
log_id | string | Unique identifier for each anomaly log entryunique | LOG-001 |
vehicle_id | string | Unique identifier for the vehicle in the fleet | VEH-1001 |
sensor_id | string | Unique identifier for the IoT sensor reporting the anomaly | SEN-temperature-01 |
sensor_type | string | Type of sensor (e.g., temperature, vibration, GPS, fuel)7 values | temperature |
anomaly_type | string | Category of anomaly detected (e.g., outlier, threshold breach, missing data)6 values | threshold_breach |
anomaly_description | string | Detailed description of the anomaly eventoptional | Engine temperature exceed… |
vehicle_status | string | Operational status of the vehicle at anomaly time (e.g., moving, idle, maintenance)moving · idle · maintenance · offline · other · optional | moving |
resolution_notes | string | Notes or actions taken to resolve the anomalyoptional | Vehicle stopped and engin… |
| Numbers 6 columns | |||
anomaly_severity | integer | Severity level of the anomaly (1=Low, 2=Medium, 3=High, 4=Critical)1 to 4 | 4 |
sensor_value | float | Sensor reading at the time of anomalyoptional | 180.5 |
expected_value_range_min | float | Minimum expected value for the sensor under normal conditionsoptional | 10 |
expected_value_range_max | float | Maximum expected value for the sensor under normal conditionsoptional | 120 |
location_latitude | float | Latitude coordinate of the vehicle at anomaly detection-90 to 90 · optional | 37.7749 |
location_longitude | float | Longitude coordinate of the vehicle at anomaly detection-180 to 180 · optional | -122.4194 |
| Dates and times 2 columns | |||
timestamp | datetime | Date and time when the anomaly was detected | 2024-06-01T10:23:00Z |
resolution_timestamp | datetime | Date and time when the anomaly was resolvedoptional | 2024-06-01T11:02:00Z |
| True or false 1 column | |||
resolved | boolean | Indicates whether the anomaly has been resolved | true |
Use it for
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.
- Logs120LOG-00110temperat…LOG-002gpsLOG-00320fuel
A software demo
Believable logs with vehicle_
id, sensor_ id and sensor_ type to fill a screen in front of a buyer.
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.
- 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.
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