Telecom Network Alarm Prioritization
This dataset provides detailed records of telecom network alarm events, including priority scores, affected services, network elements, and comprehensive resolution logs. It enables automated alarm triage, root cause analysis, and performance monitoring, supporting proactive network management and rapid incident response.
Sample rows
preview · 8 of 200 rows · all 21 columns| alarm_idstring | priority_levelstring | priority_scorefloat | is_resolvedboolean | network_element_typestring | alarm_typestring | detected_atdatetime | resolved_atdatetime | affected_service_idstring | affected_service_namestring | affected_service_typestring | network_element_idstring | location_site_idstring | location_citystring | location_statestring | location_countrystring | resolved_by_user_idstring | resolution_time_minutesfloat | alarm_source_systemstring | alarm_descriptionstring | resolution_summarystring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ALRM00001 | Critical | 11.3 | true | Router | Hardware Failure | 2024-06-15T09:14:32Z | 2024-06-15T10:03:22Z | SVC_9231 | Corporate Data Backbone | Data | NET_24583 | SITE_1102 | Dallas | TX | USA | USR102 | 48.83 | InfraGuard | Main router hardware failure detected, core network traffic affected. | Replaced faulty hardware module and restored network routing. |
| ALRM00002 | High | 7.9 | true | Sensor | Environmental Alert | 2024-06-11T13:30:01Z | 2024-06-11T15:07:49Z | SVC_1228 | Primary Data Center | Data | NET_87342 | SITE_4102 | Oslo | blank | Norway | USR211 | 97.8 | EnviroMonitor | Temperature sensor reported abnormal rise in core facility. | Adjusted HVAC settings to bring temperatures back to normal. |
| ALRM00003 | Critical | 10.7 | true | Server | Power Outage | 2024-06-18T17:48:54Z | 2024-06-18T21:33:12Z | SVC_1340 | Online Payment Gateway | Internet | NET_49913 | SITE_2095 | Chicago | IL | USA | USR347 | 224.3 | Sysmon | Unexpected power loss in data hall B. Backup generators started. | Restored main power; transitioned back from generator backup. |
| ALRM00004 | Critical | 9.2 | true | Gateway | Service Unavailable | 2024-06-12T07:20:10Z | 2024-06-12T08:19:21Z | SVC_1485 | SMS Messaging Core | SMS | NET_33201 | SITE_3200 | Frankfurt | blank | Germany | USR067 | 59.18 | SMSSupervisor | Core messaging SMS service unreachable by multiple clients. | Restarted gateway server and re-established service connectivity. |
| ALRM00005 | Low | 1.1 | true | Gateway | Scheduled Maintenance | 2024-06-16T22:01:31Z | 2024-06-17T01:45:50Z | SVC_1992 | Enterprise DB | Other | NET_50432 | SITE_1204 | London | blank | UK | USR215 | 224.32 | Maintenance Scheduler | Routine scheduled maintenance for core database cluster. | Maintenance completed, all systems verified operational. |
| ALRM00006 | Medium | 5.1 | true | Switch | Connectivity Issue | 2024-06-13T14:45:23Z | 2024-06-13T15:23:19Z | SVC_2408 | Branch WAN | Data | NET_19423 | SITE_2151 | Mumbai | MH | India | USR122 | 37.93 | NOC Sentinel | Intermittent packet loss detected on WAN link. | Reconfigured routing tables to stabilize WAN link. |
| ALRM00007 | Medium | 6.2 | true | Access Point | Performance Degradation | 2024-06-10T09:53:44Z | 2024-06-10T10:12:18Z | SVC_3049 | Customer Web Portal | Internet | NET_82391 | SITE_1403 | Madrid | blank | Spain | SYS_NOC | 18.57 | NetPerfTracker | High latency detected in customer-facing portal. | Optimized server resource allocation and cleared bottlenecks. |
| ALRM00008 | Critical | 9.7 | true | Router | Link Down | 2024-06-19T03:14:29Z | 2024-06-19T04:32:14Z | SVC_2127 | Regional WAN | Data | NET_17203 | SITE_5109 | Houston | TX | USA | USR473 | 77.75 | InfraGuard | WAN uplink to regional office is down. | Repaired uplink cable and restored connectivity. |
| ALRM00009 | Low | 2.8 | true | IoT Gateway | Firmware Update Required | 2024-06-05T21:43:15Z | 2024-06-05T21:43:49Z | SVC_4120 | IoT Sensors Network | Other | NET_61320 | SITE_9100 | Tokyo | blank | Japan | USR390 | 0.57 | PipelineTester | Critical firmware update pending on edge gateway. | Updated firmware and ran validation checks on device. |
| ALRM00010 | High | 7.1 | true | Firewall | Intrusion Detected | 2024-06-07T02:12:32Z | 2024-06-07T02:57:18Z | SVC_0318 | Corporate VPN | Data | NET_39210 | SITE_4073 | Beijing | BJ | China | USR079 | 44.77 | SecuGuard | Firewall reported unauthorized access attempt. | Blocked source IP, enhanced firewall rules. |
| ALRM00011 | Low | 0.4 | true | blank | Test Alarm | 2024-06-17T14:23:05Z | 2024-06-17T14:23:06Z | SVC_0091 | blank | Other | NET_00000 | blank | blank | blank | Null Island | SYS_TEST | 0.016 | PipelineTester | System-generated test alarm for monitoring validation. | Test alarm auto-closed after validation script execution. |
| ALRM00012 | High | 8.8 | false | Storage Array | Power Outage | 2024-06-14T22:11:39Z | blank | SVC_1047 | Mission Critical App | Internet | NET_84275 | SITE_7001 | Seattle | WA | USA | blank | blank | Sysmon | Partial power outage in server room, backup power engaged. | blank |
| ALRM00013 | Medium | 5.7 | true | Sensor | Environmental Alert | 2024-06-14T02:01:19Z | 2024-06-14T03:40:16Z | SVC_1455 | Remote Site Sensors | Other | NET_72861 | SITE_2309 | Almaty | blank | Kazakhstan | USR303 | 98.95 | FloodSense | Flood warning issued by facility ground sensor. | Inspected site, flood risk mitigated, sensors reset. |
| ALRM00014 | Critical | 12 | true | Server | Hardware Failure | 2024-06-09T17:04:41Z | 2024-06-09T18:02:16Z | SVC_8732 | Finance Transaction Engine | Data | NET_41820 | SITE_3219 | New York | NY | USA | USR112 | 57.58 | InfraGuard | Critical server disk failure leading to service interruption. | Replaced disk and restored system from backup. |
| ALRM00015 | Low | 2.3 | true | Simulated Node | Scheduled Maintenance | 2024-06-15T01:35:40Z | 2024-06-15T03:51:12Z | SVC_3501 | Backbone Switches | Other | NET_90231 | SITE_3050 | Quito | blank | Ecuador | USR217 | 135.53 | Maintenance Scheduler | Monthly network switch firmware maintenance. | Firmware updated, no errors, system verified. |
| ALRM00016 | Medium | 4.3 | false | Switch | Connectivity Issue | 2024-06-18T04:23:12Z | blank | SVC_5908 | Remote VPN Access | Data | NET_29234 | SITE_5055 | Chennai | TN | India | blank | blank | VoIP Monitor | Remote office VPN experiencing packet drops. | blank |
| ALRM00017 | Low | 0.5 | true | blank | Test Alarm | 2024-06-16T10:22:11Z | 2024-06-16T10:22:12Z | SVC_1010 | blank | Other | NET_10101 | blank | blank | blank | blank | SYS_TEST | 0.017 | LegacySystem-1 | Routine test alarm for system monitoring validation. | Test alarm closed by automation after 1 second. |
| ALRM00018 | High | 8.5 | true | Base Station | Service Unavailable | 2024-06-17T18:02:59Z | 2024-06-17T19:42:30Z | SVC_5400 | Mobile Data | Data | NET_34572 | SITE_4050 | Cape Town | blank | South Africa | USR319 | 99.52 | WebAppMonitor | User-reported outage on mobile data service. | Restarted base station, restored data service. |
| ALRM00019 | Medium | 4.8 | true | Base Station | Power Outage | 2024-06-13T03:12:43Z | 2024-06-13T03:29:32Z | SVC_2002 | Rural Voice Service | Voice | NET_42280 | SITE_3111 | Delhi | DL | India | USR078 | 16.82 | Sysmon | Short power interruption at remote cell tower. | Power restored; base station rebooted. |
| ALRM00020 | Critical | 10.1 | false | Storage Array | Hardware Failure | 2024-06-08T11:13:27Z | blank | SVC_1182 | Cloud Storage | Data | NET_70892 | SITE_5302 | San Jose | CA | USA | blank | blank | InfraGuard | Storage array disk error detected, data redundancy impacted. | blank |
What the 200 rows show
from the 200-row sampleLow (priority level) stands out: mean priority_
- 86%is_
resolved = true - 6.8median priority_
score - 5affected service types
- 14alarm types
- 14alarm source systems
- 19location countries
Median 6.8, from 0.16 to 12.0.
- string 16
- float 2
- datetime 2
- boolean 1
Columns
21 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 16 columns | |||
alarm_id | string | Unique identifier for the network alarm eventunique | ALRM00001 |
alarm_type | string | Type or category of the alarm (e.g., hardware failure, connectivity issue) | Hardware Failure |
alarm_description | string | Detailed description of the alarm eventoptional | Main router hardware fail… |
priority_level | string | Categorical priority level (e.g., Critical, High, Medium, Low)Critical · High · Medium · Low | Critical |
affected_service_id | string | Identifier for the affected network service | SVC_9231 |
affected_service_name | string | Name of the affected network serviceoptional | Corporate Data Backbone |
affected_service_type | string | Type of service impacted (e.g., Voice, Data, SMS, Internet)Voice · Data · SMS · Internet · Other · optional | Data |
network_element_id | string | Identifier for the network element (e.g., device, node) where the alarm originated | NET_24583 |
network_element_type | string | Type of network element (e.g., Router, Switch, Base Station)12 types · optional | Router |
location_site_id | string | Identifier for the physical site/location of the network elementoptional | SITE_1102 |
location_city | string | City where the alarm occurredoptional | Dallas |
location_state | string | State or region where the alarm occurredoptional | TX |
location_country | string | Country where the alarm occurredoptional | USA |
resolution_summary | string | Summary of the resolution steps taken to address the alarmoptional | Replaced faulty hardware … |
resolved_by_user_id | string | Identifier of the user or system that resolved the alarmoptional | USR102 |
alarm_source_system | string | Name of the system or application that generated the alarmoptional | InfraGuard |
| Numbers 2 columns | |||
priority_score | float | Numerical score indicating the priority or severity of the alarm (higher means more urgent)0 or more | 11.3 |
resolution_time_minutes | float | Time taken to resolve the alarm, in minutes0 or more · optional | 48.83 |
| Dates and times 2 columns | |||
detected_at | datetime | Timestamp when the alarm was detected | 2024-06-15T09:14:32Z |
resolved_at | datetime | Timestamp when the alarm was resolved (null if unresolved)optional | 2024-06-15T10:03:22Z |
| True or false 1 column | |||
is_resolved | boolean | Indicates whether the alarm has been resolved | true |
Use it for
A telecommunications dashboard
The is_
resolved rate, priority_ score by priority_ level and a breakdown of network_ element_ type. Excel, Power BI or Tableau. Why do the 53 Low rows have a mean priority_
score of 1.8? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Alarms200ALRM0000111.3CriticalALRM000027.9HighALRM000128.8High
A software demo
Believable alarms with alarm_
type, alarm_ description and priority_ score to fill a screen in front of a buyer.
This dataset200 rows21 columns
Yours10,000 rows21 columnslocation_site_id: UK only
blueprint · telecom-network-alarm-prioritization
Behind this dataset
Same schema. As many rows as you need.
These 200 rows came out of a blueprint — 21 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 alarm: timestamp, location, type, severity
- Priority assigned based on impact rules
- Affected service/customer count logged
- Resolution time and root cause included
- False positives marked
Open the blueprint in Data Factory
1 credit per row. New accounts start with 25 free credits.
- Exports
- CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
- Licence
- yours to use, including commercially
- API slug
- telecom-network-alarm-prioritization