IoT Sensor Fault Detection Logs

This dataset provides detailed logs of sensor faults across an IoT network, including event timing, fault types, severity, sensor/device identification, location, and resolution actions. It enables predictive maintenance, reliability analysis, and operational monitoring for large-scale sensor deployments, supporting research and real-time analytics for improved uptime and efficiency.

  • last updated 21 Aug 2025
  • by GoMask
The brief that made it

Predictive maintenance and failure prevention

Sample rows

preview · 8 of 200 rows · all 18 columns
event_idstringfault_severitystringresolvedbooleandevice_idstringsensor_idstringlocation_latitudefloatlocation_longitudefloatlocation_descriptionstringfault_typestringevent_timestampdatetimesensor_typestringsensor_modelstringfirmware_versionstringlast_maintenance_datedateresolution_timestampdatetimeresolution_actionstringreported_bystringfault_descriptionstring
EVT-0001criticaltrueDV-GW-01SNS-ALPHA-00140.7128-74.006NYC, Main Facility, Zone 2signal_loss2024-04-03T09:24:31ZtemperatureTempMax-3000v2.4.12024-03-152024-04-03T10:01:12Zsensor replacedsystem_autoSensor signal intermittently lost during peak operation hours.
EVT-0002criticaltrueDV-GW-02SNS-BETA-00252.5213.405Berlin, Logistics Centerhardware_failure2024-05-14T08:51:08ZhumidityHumidX-100v1.9.32024-05-012024-05-14T09:13:47Zsensor replacedmaintenance-teamHumidity sensor hardware failure detected by auto diagnostics.
EVT-0003criticaltrueDV-GW-03SNS-GAMMA-00335.6895139.6917Tokyo, Plant Wing Apower_failure2024-06-01T21:33:16ZpressurePressSure-P210v3.0.02024-05-182024-06-01T22:04:22Zreplaced fusesystem_autoPressure sensor experienced unexpected power interruption.
EVT-0004warningtrueDV-GW-04SNS-DELTA-00451.5074-0.1278London, Section Bcalibration_error2024-06-09T17:41:49ZtemperatureTempMax-5000v2.5.22024-05-292024-06-09T18:10:03Zrecalibratedmaintenance-teamTemperature readings outside expected range; recalibration required.
EVT-0005warningfalseDV-GW-01SNS-ALPHA-00140.7128-74.006NYC, Main Facility, Zone 2out_of_range2024-04-21T13:15:44ZtemperatureTempMax-3000v2.4.12024-04-01blankblankfield-opTemperature values exceeded upper safety threshold during afternoon cycle.
EVT-0006warningfalseDV-GW-05SNS-EPSILON-00548.85662.3522Paris, Backup Storagecommunication_error2024-03-27T11:22:37ZmotionMotionPro-M200v4.2.02024-03-13blankblanksvc.techIntermittent communication drops detected between sensor and gateway.
EVT-0007criticaltrueDV-GW-06SNS-ZETA-00641.902812.4964Rome, Field Arraysignal_loss2024-05-04T15:56:11ZmotionMotionPro-M200v4.2.02024-04-122024-05-04T16:30:45Zresetsystem_autoSignal loss from motion sensor in field array during night cycle.
EVT-0008criticaltrueDV-GW-07SNS-THETA-00734.0522-118.2437LA, Plant Deck 3hardware_failure2024-04-20T19:46:54ZvibrationVibeSense-VS100v1.2.12024-04-012024-04-20T20:21:19Zsensor replacedmaintenance-teamVibration sensor failed self-diagnostic check; hardware replacement required.

What the 200 rows show

from the 200-row sample

Critical (fault severity) stands out: 76 of its 101 rows have resolved = true, against 29 of 99 for the rest.

  • 53%resolved = true
  • 6resolution actions
  • 7sensor types
  • 10fault types
  • 10reported_by values
  • 18sensor models
Resolved rate by fault_severityresolved = true
0%50%100%75%critical76 of 10141%warning25 of 6111%info4 of 38
device_id186 rows with a value · 14 left blank
  1. DV-GW-0722
  2. DV-GW-0514
  3. DV-GW-0212
  4. DV-GW-0311
  5. DV-GW-0911
  6. DV-GW-1411
  7. DV-GW-1511
  8. DV-GW-049
  9. DV-GW-069
  10. DV-GW-119
18 columns by typefrom the column list below
  • string 12
  • float 2
  • date 1
  • datetime 2
  • boolean 1

Columns

18 columns in four groups
blueprint · 18 columns
columntypedescriptionexample
Text 12 columns
event_idstringUnique identifier for each fault event log entryuniqueEVT-0001
sensor_idstringUnique identifier for the sensor reporting the faultSNS-ALPHA-001
device_idstringIdentifier for the device or gateway hosting the sensoroptionalDV-GW-01
location_descriptionstringHuman-readable description of the sensor location (e.g., 'Warehouse A, Section 3')optionalBerlin, Logistics Center
fault_typestringType/category of the fault detected (e.g., 'signal_loss', 'out_of_range', 'hardware_failure')7 valuessignal_loss
fault_severitystringSeverity level of the fault (e.g., 'critical', 'warning', 'info')critical · warning · infocritical
sensor_typestringType of sensor (e.g., 'temperature', 'humidity', 'pressure', 'motion')7 values · optionaltemperature
sensor_modelstringManufacturer/model of the sensoroptionalTempMax-3000
firmware_versionstringFirmware version running on the sensoroptionalv2.4.1
fault_descriptionstringDetailed description or notes about the fault eventoptionalSensor signal intermitten…
resolution_actionstringAction taken to resolve the fault (e.g., 'sensor replaced', 'recalibrated', 'reset')6 actions · optionalsensor replaced
reported_bystringIdentifier or name of the system/user reporting the fault10 values · optionalsystem_auto
Numbers 2 columns
location_latitudefloatLatitude coordinate of the sensor location-90 to 90 · optional40.7128
location_longitudefloatLongitude coordinate of the sensor location-180 to 180 · optional-74.006
Dates and times 3 columns
event_timestampdatetimeDate and time when the fault event was detected2024-04-03T09:24:31Z
last_maintenance_datedateDate when the sensor was last maintained or servicedoptional2024-03-15
resolution_timestampdatetimeDate and time when the fault was resolved (if applicable)optional2024-04-03T10:01:12Z
True or false 1 column
resolvedbooleanIndicates whether the fault has been resolvedtrue

Use it for

  • resolved53%105 of 200 rowsresolved by fault sev…75%critic…41%warning11%info

    A manufacturing dashboard

    The resolved rate, resolved by fault_severity and a breakdown of device_id. Excel, Power BI or Tableau.

  • Why do 105 of 200 rows have resolved = true?

    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 events with sensor_id, device_id and location_latitude to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 18 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 dataset200 rows18 columns
Yours1,000 rows18 columnslocation_latitude: UK only

blueprint · iot-sensor-fault-detection-logs

Behind this dataset

Same schema. As many rows as you need.

These 200 rows came out of a blueprint — 18 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 log includes device ID, fault type
  • Timestamp must be UTC
  • Critical faults escalated
  • Devices with >5 faults flagged
  • Recovery actions logged
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
iot-sensor-fault-detection-logs

More in Manufacturing

Browse all
Also in ManufacturingFactory IoT Sensor Event LogsManufacturing Predictive Maintenance RecordsEquipment MaintenanceAll 1,958 datasets

What should your data show?

Preview 20 rows free
No signup. No card.