Network Element Alarms and Fault Management

This dataset provides real-time, structured records of network element alarms and fault management events, including severity, type, affected equipment, timestamps, root cause analysis, and alarm correlations for automated troubleshooting. It enables proactive network monitoring, rapid incident response, and advanced analytics for reliability and performance optimization.

  • opened 12 times
  • last updated 1 Nov 2025
  • by GoMask
The brief that made it

Automated network fault detection and troubleshooting

Sample rows

preview · 8 of 900 rows · all 11 columns
alarm_idstringnetwork_element_typestringalarm_typestringseveritystringnetwork_element_idstringtimestampdatetimeclearance_timedatetimecorrelated_alarm_idsstringauto_troubleshooting_statusstringroot_causestringdescriptionstring
ALM001routerhardware failurecriticalNE10012024-06-01T02:17:38Z2024-06-01T04:29:12ZALM003,ALM023failedMainboard malfunction detected after power surge.A hardware failure was detected on router NE1001, causing immediate loss of connectivity. Manual intervention required to replace faulty hardware.
ALM002gatewayconnectivity lossmajorNE20022024-06-01T06:57:59Z2024-06-01T09:08:22ZALM017completedFiber cut between site and backbone detected.Gateway NE2002 lost connectivity due to backbone fiber cut. Issue resolved after rerouting traffic and repairing the fiber.
ALM003routerpower outagecriticalNE10012024-06-01T02:15:17Z2024-06-01T03:01:58ZALM001failedUnplanned power outage at local datacenter.Router NE1001 experienced a power outage, resulting in hardware shutdown. Power restored after maintenance team intervention.
ALM004eNodeBhigh temperatureminorNE30032024-05-30T14:22:43ZblankblankinitiatedAir conditioning unit failure in equipment shelter.High temperature detected on eNodeB NE3003. Automated cooling procedures initiated; issue ongoing and under monitoring.
ALM005gatewaysoftware crashmajorNE40042024-05-29T19:08:13Z2024-05-29T22:17:41ZALM028completedUnexpected exception triggered by corrupted database entry.Gateway NE4004 software crashed due to database corruption. Reboot and database restore resolved the issue.
ALM006routerconfiguration warningminorNE50052024-06-03T08:34:24ZblankblankinitiatedDeprecated configuration detected during routine audit.Router NE5005 issued a configuration warning for obsolete settings. Monitoring continues for potential service impact.
ALM007gatewaydisk failurecriticalNE60062024-06-02T11:43:32ZblankALM031failedSSD failure due to wear-out after extended usage.Gateway NE6006 suffered a disk failure. Data migration and recovery procedures are in progress, manual replacement required.
ALM008eNodeBlicense warningwarningNE70072024-06-04T13:15:55Z2024-06-04T13:27:01ZblankcompletedLicense for feature set expiring in 7 days.License warning on eNodeB NE7007. Notification sent to administrator for renewal prior to expiration.

What the 900 rows show

from the 900-row sample
  • 3auto troubleshooting statuses
  • 4severities
  • 135network elements
network_element_type900 rows by value
0180360229eNodeB25%315router35%356gateway40%
alarm_type900 rows · top 10 of 20 values
  1. hardware failure62
  2. connectivity loss60
  3. software crash58
  4. license warning56
  5. configuration warning52
  6. service degradation51
  7. malware detected50
  8. disk failure49
  9. fan failure49
  10. CPU overload46
11 columns by typefrom the column list below
  • string 9
  • datetime 2

Columns

11 columns in two groups
blueprint · 11 columns
columntypedescriptionexample
Text 9 columns
alarm_idstringUnique identifier for each alarm eventuniqueALM001
severitystringSeverity level of the alarmcritical · major · minor · warningcritical
alarm_typestringType or category of the alarm (e.g., hardware failure, connectivity loss)hardware failure
network_element_idstringUnique identifier for the affected network elementNE1001
network_element_typestringType of network element affected (eNodeB, router, gateway)eNodeB · router · gatewayrouter
root_causestringSummary of the root cause analysis for the alarmoptionalPower module failure.
correlated_alarm_idsstringComma-separated list of related alarm IDs for correlation and automated troubleshootingoptionalALM003,ALM023
auto_troubleshooting_statusstringStatus of automated troubleshooting (e.g., initiated, completed, failed)initiated · completed · failed · optionalfailed
descriptionstringDetailed description of the alarm eventoptionalA hardware failure was de…
Dates and times 2 columns
timestampdatetimeDate and time when the alarm was triggered2024-06-01T02:17:38Z
clearance_timedatetimeDate and time when the alarm was cleared/resolvedoptional2024-06-01T04:29:12Z

15 SQL practice questions for the Network Element Alarms and Fault Management

Written for this data and checked against it: 12 SQL and 3 Power BI exercises from beginner to advanced. Try the first three free; the practice kit has all 15, a starter .sql file and an answer key with every expected result.

  1. 01BeginnerFreeSELECT · WHERE · ORDER BY

    Critical router alarms

    Return alarm_id, network_element_id and timestamp for every alarm whose severity is 'critical' and whose network_element_type is 'router'. Order the results by timestamp ascending, then by alarm_id ascending.

    Tables: network_element_alarms_and_fault_management · your result: 3 columns, 94 rows
  2. 02BeginnerFreeDISTINCT · ORDER BY

    Distinct alarm types

    Return each distinct alarm_type found in the data as a single column named alarm_type, sorted alphabetically.

    Tables: network_element_alarms_and_fault_management · your result: 1 columns, 20 rows
  3. 03BeginnerFreeGROUP BY · COUNT

    Alarms per severity

    Count the alarms for each severity. Return severity and alarm_count, ordered by alarm_count descending, then by severity ascending.

    Tables: network_element_alarms_and_fault_management · your result: 2 columns, 4 rows
  1. 04Failed alarms missing a root causeBeginner
  2. 05Open alarms by element typePower BI
  3. 06Alarm types with many alarmsIntermediate
  4. 07Resolution time bucketsIntermediate
  5. 08Alarms per monthIntermediate
  6. 09Elements above average alarm countIntermediate
  7. 10Failure rate by alarm typePower BI
  8. 11Rank alarm types within severityAdvanced
  9. 12Gap since previous alarm on elementAdvanced
  10. 13Running monthly alarm totalAdvanced
  11. 14Percent of alarms by element typeAdvanced
  12. 15Slowest clearance anomaliesPower BI

Get the practice kit: the full dataset, all 15 exercises, a starter .sql and the answer key. One-time $3.99.

Get the practice kit · $3.99

Use it for

  • rows90011 columnsrows by network eleme…229eNodeB315router356gateway

    A telecommunications dashboard

    A breakdown of alarm_type. Excel, Power BI or Tableau.

  • What pattern can you find in 900 rows?

    A class exercise

    Hand out the rows and one question. Everyone works from the same 900 rows.

  • A software demo

    Believable alarms with severity, alarm_type and network_element_id to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 11 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 dataset900 rows11 columns
Yours1,000 rows11 columns

blueprint · network-element-alarms-and-fault-management

Behind this dataset

Same schema. As many rows as you need.

These 900 rows came out of a blueprint — 11 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
  • Alarm ID and sequence number
  • Severity: critical (service down), major, minor, warning, informational
  • Alarm type: equipment failure, link down, high CPU, high temperature, power loss
  • Affected network element: eNodeB, router, switch, gateway, server
  • Alarm timestamp (raised) and clearance timestamp (resolved)
  • Alarm state: active, acknowledged, cleared, escalated
  • Root cause: correlated with other alarms, identified cause
  • Impact: customers affected, services impacted, geographic area
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
network-element-alarms-and-fault-management

More in Telecommunications

Browse all
Also in TelecommunicationsTrouble Ticket Management and Resolution TrackingTelecom Call Drop DiagnosticsNetwork Performance Degradation and Quality IssuesAll 1,967 datasets

What should your data show?

Preview 20 rows free
No signup. No card.