Alarms
Alarm creation and monitoring
Alarm creation and monitoring focus on how alarms are generated and observed within the system. This process includes different methods for creating alarms and options for monitoring their status.
- Automatic creation: Alarms are generated by FMS when thresholds are breached.
- API-based creation: Primary and secondary alarms can be created via REST API.
- Monitoring: Alarms can be monitored through the UI or REST API for status and details.
Alarm types
Alarm types classify alarms by their purpose and help with accurate prioritization, routing, and remediation in telecom operations. These types can be triggered via APIs and are used to indicate the nature of the underlying condition.
| Alarm type | Purpose |
|---|---|
| communicationsAlarm | Indicates issues in communication paths or signaling between network elements. Common in scenarios like link failures or protocol mismatches. |
| processingErrorAlarm | Indicates software or processing faults within network or control systems. For example, application errors, transaction failures |
| environmentalAlarm | Indicates the arlarm is triggered by environmental conditions affecting equipment, such as temperature, humidity, or power fluctuations. |
qualityOfServiceAlarm | Signals degradation in service quality, such as latency, packet loss, impacting customer experience. |
| equipmentAlarm | Generated when hardware components fail or malfunction, such as routers, switches, or transmission equipment. |
| integrityViolation | Indicates data integrity issues, such as corrupted configurations or unauthorized changes to system parameters. |
| operationalViolation | Occurs when operational policies or procedures are violated, such as exceeding capacity thresholds or improper configurations. |
| physicalViolation | Flags physical security or infrastructure integrity is compromised, such as unauthorized access to equipment rooms. |
| securityService | Indicates the Alert related to security services, such as authentication failures, or encryption issues. |
| mechanismViolation | Indicates failure or misuse of security mechanisms, such as incorrect key management or protocol enforcement. |
| timeDomainViolation | Reports timing/synchronization breaches impacting time-sensitive services, such as synchronization errors in VoLTE service. |
Alarm-to-Incident workflow
When an alarm is created through the REST API or detected by the Fault Management System (FMS), an incident is automatically generated in Incident Management. The alarm details are displayed in the incident record, providing visibility into the underlying condition. The severity of the alarm linked to the incident is updated automatically through the API, ensuring that the incident priority remains accurate and reflects the latest alarm state.