Farm IoT Sensor Failure Logs

This dataset provides granular logs of IoT sensor failures across agricultural farms, detailing device types, failure categories, downtime, resolution actions, and environmental context. It is designed to support predictive maintenance, minimize operational disruptions, and guide technology investments for sustainable farming. The schema enables startups and farm operators to analyze patterns, optimize sensor reliability, and improve farm data collection consistency.

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

Predictive maintenance modeling for farm IoT sensors

Sample rows

preview · 8 of 60 rows · all 19 columns
failure_idstringfailure_severitystringdowntime_minutesintegerresolvedbooleantechnician_idstringsensor_idstringdevice_typestringfarm_idstringfarm_namestringlocation_latitudefloatlocation_longitudefloatfailure_datetimedatetimefailure_typestringfailure_descriptionstringresolution_datetimedatetimeresolution_actionstringpreventive_action_flagbooleanenvironmental_conditionsstringsensor_installation_datedate
F-8134ABCDmajor180trueTECH-21S-1001XZsoil-moistureFARM-001River Valley Farms41.6724-93.69922024-05-01T08:17:00hardwareSensor casing cracked due to prolonged exposure.2024-05-01T12:05:00replacedtrueHigh UV index, dry soil2023-04-14
F-2938KLMPminor22trueTECH-13S-1002YZtemperatureFARM-002Green Acres38.9847-92.3292024-05-03T16:34:00connectivityBrief signal dropout detected.2024-05-03T16:56:00resetfalseLight rain, low signal2023-07-02
F-9281QWERcritical492trueTECH-09S-1003JKhumidityFARM-003Sunny Fields36.9932-86.43212024-05-07T11:09:00powerSensor battery depleted unexpectedly.2024-05-07T19:21:00replacedtrueCloudy, moderate temperature2023-10-10
F-4567ZXCVmajor0falseblankS-1004RTweather-stationFARM-004Prairie Orchards39.1832-91.23912024-05-11T07:22:00calibrationWind speed readings out of expected range.blanknonefalseCalm winds, clear sky2022-12-20
F-7890FDGHminor55trueTECH-19S-1005LMph-sensorFARM-002Green Acres38.9871-92.3282024-05-13T13:40:00environmentalSensor flooded after heavy rainfall.2024-05-13T14:35:00repairedtrueHeavy rain, saturated soil2023-08-15
F-8901GHJKcritical210trueTECH-06S-1006OPsoil-moistureFARM-005Blue Sky Ranch40.2518-95.11922024-05-15T09:24:00hardwareProbe corroded, unable to measure moisture.2024-05-15T12:54:00replacedtrueWet soil, recent irrigation2023-09-05
F-1234MNBVminor12trueTECH-17S-1007QRtemperatureFARM-001River Valley Farms41.6738-93.70122024-05-18T15:12:00connectivitySensor lost WiFi connection.2024-05-18T15:24:00resetfalseMild wind, clear2023-07-19
F-5678PLKMmajor80trueTECH-01S-1008STotherFARM-006Orchard Lane Estate42.1247-94.22142024-05-21T06:45:00powerUnexpected power surge during maintenance.2024-05-21T08:05:00resetfalseCloudy, low humidity2023-05-29

What the 60 rows show

from the 60-row sample

Critical (failure severity) stands out: mean downtime_minutes is 245.6, against 40.2 for the rest.

  • 98%resolved = true
  • 48.5median downtime_minutes
  • 5resolution actions
  • 6device types
  • 6failure types
Mean downtime_minutes by failure_severity60 rows
020040014.5minor22 rows66.0major22 rows245.6critical16 rows
downtime_minutes60 rows, in bands of 100
02550439322010400700downtime_minutes →

Median 48.5, from 0 to 610.

technician_id59 rows with a value · 1 left blank
  1. TECH-05B5
  2. TECH-09D5
  3. TECH-17E4
  4. TECH-14F4
  5. TECH-20A4
  6. TECH-093
  7. TECH-103
  8. TECH-223
  9. TECH-073
  10. TECH-21C3
19 columns by typefrom the column list below
  • string 11
  • integer 1
  • float 2
  • date 1
  • datetime 2
  • boolean 2

Columns

19 columns in four groups
blueprint · 19 columns
columntypedescriptionexample
Text 11 columns
failure_idstringUnique identifier for each sensor failure eventuniqueF-8134ABCD
sensor_idstringUnique identifier for the IoT sensor deviceS-1001XZ
device_typestringType of IoT device (e.g., soil-moisture, weather-station, temperature, humidity)6 valuessoil-moisture
farm_idstringUnique identifier for the farm where the sensor is deployedFARM-001
farm_namestringName of the farm where the sensor is locatedoptionalRiver Valley Farms
failure_typestringCategory of failure (e.g., hardware, connectivity, power, calibration, environmental)6 valueshardware
failure_severitystringSeverity level of the failure (e.g., minor, major, critical)minor · major · criticalmajor
failure_descriptionstringDetailed description of the failure eventoptionalSensor tip fractured.
resolution_actionstringAction taken to resolve the failure (e.g., replaced, repaired, reset, recalibrated)6 values · optionalreplaced
technician_idstringIdentifier for the technician or team responsible for resolutionoptionalTECH-21
environmental_conditionsstringSummary of environmental conditions at the time of failure (e.g., rain, high humidity, extreme temperature)optionalHigh UV index, dry soil
Numbers 3 columns
location_latitudefloatLatitude coordinate of the sensor's location-90 to 9041.6724
location_longitudefloatLongitude coordinate of the sensor's location-180 to 180-93.6992
downtime_minutesintegerTotal downtime in minutes caused by the failure0 or more · optional180
Dates and times 3 columns
failure_datetimedatetimeTimestamp when the sensor failure was detected2024-05-01T08:17:00
resolution_datetimedatetimeTimestamp when the failure was resolvedoptional2024-05-01T12:05:00
sensor_installation_datedateDate when the sensor was installedoptional2023-04-14
True or false 2 columns
resolvedbooleanIndicates whether the failure has been resolvedtrue
preventive_action_flagbooleanIndicates if a preventive action was taken post-failureoptionaltrue

Use it for

  • resolved98%59 of 60 rowsmean downtime minutes…14.5minor66.0major245.6critic…

    An agriculture dashboard

    The resolved rate, downtime_minutes by failure_severity and a breakdown of technician_id. Excel, Power BI or Tableau.

  • Why do the 16 critical rows have a mean downtime_minutes of 245.6?

    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 failures with sensor_id, device_type and farm_id to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 19 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 dataset60 rows19 columns
Yours1,000 rows19 columnslocation_latitude: UK only

blueprint · farm-iot-sensor-failure-logs

Behind this dataset

Same schema. As many rows as you need.

These 60 rows came out of a blueprint — 19 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 single sensor failure or anomaly event
  • Include device type, location (field/block), and failure time
  • Log root cause classification (hardware/software/environmental)
  • Record resolution time and maintenance action taken
  • Sensors must be active on commercial farms; exclude prototypes
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
farm-iot-sensor-failure-logs

What should your data show?

Preview 20 rows free
No signup. No card.