Social Media Data Center IoT Alerts
This dataset provides detailed, structured records of IoT alert events from social media platform data centers, including device information, alert types and severities, response metrics, and resolution details. It enables IT managers to monitor device health, detect security incidents, and optimize maintenance workflows for distributed edge environments. The dataset supports proactive risk mitigation, incident response analysis, and operational reporting.
Sample rows
preview · 8 of 120 rows · all 22 columns| alert_idstring | alert_severitystring | time_to_acknowledge_minutesinteger | is_escalatedboolean | assigned_tostring | alert_timestampdatetime | data_center_idstring | data_center_namestring | data_center_location_citystring | data_center_location_statestring | data_center_location_countrystring | device_idstring | device_typestring | device_modelstring | device_firmware_versionstring | alert_typestring | alert_statusstring | detected_bystring | time_to_resolve_minutesinteger | related_ticket_idstring | alert_descriptionstring | resolution_notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ALRT-0001 | high | blank | false | blank | 2022-01-01T02:15:31Z | DC-NYC-01 | New York Central DC | New York | NY | US | DV-SEN-101 | sensor | TempSense-X100 | v2.3.1 | device_health | new | device_agent | blank | blank | Temperature sensor reported unexpected fluctuation in readings. | blank |
| ALRT-0002 | critical | 3 | true | sec_ops_team | 2024-02-13T09:44:11Z | DC-SFO-03 | San Francisco Bay DC | San Francisco | CA | US | DV-CAM-210 | camera | CamPro-4K | v5.1.0 | security | escalated | monitoring_tool | blank | TCK-3831 | Unauthorized access detected at entrance, camera feed flagged. | blank |
| ALRT-0003 | critical | 2 | true | net_eng_bob | 2024-03-05T17:22:41Z | DC-BOM-12 | Mumbai Gateway DC | Mumbai | MH | IN | DV-GAT-301 | gateway | GateLink XT | v1.8.0-beta | connectivity | new | monitoring_tool | blank | TCK-4104 | Gateway lost connection to edge devices in zone 4. | blank |
| ALRT-0004 | medium | 22 | false | eng_satoshi | 2024-04-17T11:37:58Z | DC-TYO-10 | Tokyo Edge DC | Tokyo | Tokyo | JP | DV-SRV-701 | server | SrvMax-9100 | v4.7.4 | maintenance | resolved | maintenance_scheduler | 54 | blank | Server scheduled for maintenance completed successfully. | Routine server maintenance finished without incident. |
| ALRT-0005 | low | 16 | false | eng_alex | 2024-01-27T08:05:44Z | DC-LON-07 | London Main DC | London | London | GB | DV-ROU-512 | router | EdgeRoute XR | v3.0.2 | maintenance | resolved | maintenance_scheduler | 31 | blank | Router firmware updated during maintenance window. | Router firmware update completed as scheduled. |
| ALRT-0006 | high | 4 | false | sec_ops_team | 2023-12-31T23:59:59Z | DC-JHB-16 | Johannesburg Node DC | Johannesburg | GP | ZA | DV-CAM-214 | camera | CamPro-HD | v5.0.9 | security | acknowledged | device_agent | blank | blank | Camera detected motion outside normal hours. | blank |
| ALRT-0007 | info | 8 | false | net_eng_anika | 2024-04-04T15:16:02Z | DC-SNG-05 | Singapore Hub DC | Singapore | SG | SG | DV-GAT-311 | gateway | GateNano | v1.7.3 | connectivity | resolved | monitoring_tool | 13 | blank | Gateway reported temporary loss of signal, now restored. | Signal loss resolved, gateway back online. |
| ALRT-0008 | medium | 6 | false | tech_jane | 2024-03-22T10:32:47Z | DC-NYC-01 | New York Central DC | New York | NY | US | DV-SEN-105 | sensor | EnviroSense-2 | v2.4.0 | device_health | acknowledged | device_agent | blank | blank | Humidity sensor flagged for calibration drift. | blank |
| ALRT-0009 | high | 7 | false | tech_mike | 2024-04-18T14:21:47Z | DC-BOM-12 | Mumbai Gateway DC | Mumbai | MH | IN | DV-SEN-111 | sensor | EnviroSense-1 | v2.2.9 | device_health | acknowledged | device_agent | blank | blank | Sensor battery level below warning threshold. | blank |
| ALRT-0010 | critical | 5 | true | sec_ops_team | 2024-02-26T20:12:51Z | DC-JHB-16 | Johannesburg Node DC | Johannesburg | GP | ZA | DV-CAM-215 | camera | MobEye Z2 | v4.9.8 | security | escalated | monitoring_tool | blank | TCK-4020 | Camera tampering detected, immediate action required. | blank |
| ALRT-0011 | medium | blank | false | blank | 2024-02-07T07:11:23Z | DC-SFO-03 | San Francisco Bay DC | San Francisco | CA | US | DV-SEN-123 | sensor | EnviroSense-2 | v2.4.2 | device_health | new | device_agent | blank | blank | Sensor flagged for periodic health check. | blank |
| ALRT-0012 | medium | 18 | false | eng_alex | 2024-01-16T12:35:29Z | DC-LON-07 | London Main DC | London | London | GB | DV-ROU-513 | router | EdgeRoute XR | v3.0.1 | maintenance | resolved | maintenance_scheduler | 46 | blank | Router maintenance task completed successfully. | Maintenance completed, router now operating normally. |
| ALRT-0013 | critical | 5 | true | net_eng_anika | 2024-03-19T03:58:12Z | DC-SNG-05 | Singapore Hub DC | Singapore | SG | SG | DV-GAT-319 | gateway | MobLink R1 | v1.6.7 | connectivity | new | monitoring_tool | blank | TCK-4179 | Gateway unable to reach remote endpoints. | blank |
| ALRT-0014 | info | 3 | false | maint_team_1 | 2024-04-06T19:45:03Z | DC-BOM-12 | Mumbai Gateway DC | Mumbai | MH | IN | DV-SEN-140 | sensor | TempSense-X100 | v2.3.3 | other | resolved | device_agent | 9 | blank | Sensor self-test completed successfully. | Sensor passed all self-test routines. |
| ALRT-0015 | high | 12 | false | eng_satoshi | 2024-03-21T22:12:17Z | DC-TYO-10 | Tokyo Edge DC | Tokyo | Tokyo | JP | DV-SRV-711 | server | SrvMax-9000 | v4.5.1 | performance | acknowledged | monitoring_tool | blank | blank | CPU utilization exceeded defined threshold for 10 minutes. | blank |
| ALRT-0016 | medium | blank | false | blank | 2024-04-01T05:34:29Z | DC-NYC-01 | New York Central DC | New York | NY | US | DV-SEN-112 | sensor | TempSense-X100 | v2.3.2 | device_health | new | device_agent | blank | blank | Sensor periodic health check initiated. | blank |
| ALRT-0017 | critical | 6 | true | sec_ops_team | 2024-02-19T03:43:11Z | DC-SFO-03 | San Francisco Bay DC | San Francisco | CA | US | DV-CAM-218 | camera | MobEye Z2 | v4.9.9 | security | escalated | monitoring_tool | blank | TCK-3925 | Multiple failed login attempts on camera admin interface. | blank |
| ALRT-0018 | medium | 14 | false | eng_alex | 2024-02-21T09:19:57Z | DC-LON-07 | London Main DC | London | London | GB | DV-SRV-722 | server | SrvMax-9000 | v4.6.3 | performance | acknowledged | monitoring_tool | blank | blank | Memory usage has exceeded defined safe levels. | blank |
| ALRT-0019 | info | 6 | false | net_eng_bob | 2024-04-11T08:28:33Z | DC-JHB-16 | Johannesburg Node DC | Johannesburg | GP | ZA | DV-GAT-318 | gateway | GateLink XT | v1.8.1 | connectivity | resolved | monitoring_tool | 12 | blank | Gateway connection restored after brief downtime. | Brief downtime resolved, gateway stable. |
| ALRT-0020 | low | 10 | false | eng_satoshi | 2023-01-01T00:00:01Z | DC-TYO-10 | Tokyo Edge DC | Tokyo | Tokyo | JP | DV-ROU-551 | router | EdgeRoute XR | v3.0.4 | maintenance | resolved | maintenance_scheduler | 34 | blank | Router scheduled reboot completed. | Reboot completed, router back online. |
What the 120 rows show
from the 120-row sampleCritical (alert severity) stands out: 30 of its 30 rows have is_
- 30%is_
escalated = true - 7median time_
to_ acknowledge_ minutes - 3detected_
by values - 4alert statuses
- 5device types
- 6alert types
Median 7, from 0 to 41.
- string 18
- integer 2
- datetime 1
- boolean 1
Columns
22 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 18 columns | |||
alert_id | string | Unique identifier for each IoT alert event.unique | ALRT-0001 |
data_center_id | string | Unique identifier for the data center where the alert originated.8 centers | DC-NYC-01 |
data_center_name | string | Human-readable name of the data center.optional | New York Central DC |
data_center_location_city | string | City where the data center is located.8 cities · optional | New York |
data_center_location_state | string | State or region where the data center is located.11 states · optional | NY |
data_center_location_country | string | Country where the data center is located.7 countries · optional | US |
device_id | string | Unique identifier for the IoT device that generated the alert. | DV-SEN-101 |
device_type | string | Type or category of the IoT device (e.g., sensor, camera, server).5 types | sensor |
device_model | string | Model or version of the IoT device.12 models · optional | TempSense-X100 |
device_firmware_version | string | Firmware version running on the IoT device.optional | v2.3.1 |
alert_type | string | Category of the alert (e.g., device_health, security, maintenance, connectivity).6 values | device_health |
alert_severity | string | Severity level of the alert.critical · high · medium · low · info | high |
alert_status | string | Current status of the alert (e.g., new, acknowledged, resolved, escalated).new · acknowledged · resolved · escalated | new |
alert_description | string | Detailed description of the alert event.optional | Temperature sensor report… |
detected_by | string | Source or system that detected the alert (e.g., monitoring_tool, device_agent).3 values · optional | device_agent |
assigned_to | string | User ID or team responsible for handling the alert.optional | sec_ops_team |
resolution_notes | string | Notes or comments regarding the resolution of the alert.optional | Routine server maintenanc… |
related_ticket_id | string | Reference to an external incident or ticketing system ID, if applicable.optional | TCK-3831 |
| Numbers 2 columns | |||
time_to_acknowledge_minutes | integer | Time in minutes taken to acknowledge the alert.0 or more · optional | 3 |
time_to_resolve_minutes | integer | Time in minutes taken to resolve the alert.0 or more · optional | 54 |
| Dates and times 1 column | |||
alert_timestamp | datetime | Date and time when the alert was generated. | 2022-01-01T02:15:31Z |
| True or false 1 column | |||
is_escalated | boolean | Indicates if the alert was escalated for further action.optional | false |
Use it for
A technology dashboard
The is_
escalated rate, time_ to_ acknowledge_ minutes by alert_ severity and a breakdown of assigned_ to. Excel, Power BI or Tableau. Why do 36 of 120 rows have is_
escalated = true? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Alerts120ALRT-0001highALRT-00023criticalALRT-00032critical
A software demo
Believable alerts with alert_
timestamp, data_ center_ id and data_ center_ name to fill a screen in front of a buyer.
blueprint · social-media-data-center-iot-alerts
Behind this dataset
Same schema. As many rows as you need.
These 120 rows came out of a blueprint — 22 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 alert must include device ID, timestamp, severity, and alert type
- Severity levels categorized as: low, medium, high, critical
- Alerts flagged as 'security' require immediate IT escalation
- Devices reporting repeated faults (>3 in 24h) trigger maintenance recommendation
- Alert types mapped to predefined operational categories (network, power, security, hardware)
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
- social-media-data-center-iot-alerts