src/opticalcontroller/alarm_engine.py
0 → 100644File added.
Preview size limit exceeded, changes collapsed.
Alarm handling for optical devices, with optional automatic protection.
alarm_engine evaluates each KPI sample against the configured operating
ranges and holds the per-device gate that decides whether a device's alarms
are trusted yet: a device is admitted only once a genuine non-zero in-range
PRE_FEC_BER is seen together with an in-range RECEIVED_POWER, so it cannot
qualify on its start-up defaults.
Any number of pairs can be protected. On a protected device's first confirmed alarm its path is recomputed onto the backup and monitoring follows, reverting when the backup settles, its path is deleted, or a new path is computed from the protected device. With no policy configured every entry point is inert.
The policy component forwards every optical KPI sample so the controller applies the ranges itself rather than depending on Analytics' current threshold.
Closes #440 (closed)
/AlarmSubscribe receives a notification
when a monitored device leaves its configured range.src/opticalcontroller/tests/: 20 passed in the image built from this
branch; all modules import cleanly, including the mutually dependent alarm
engine and failover state machine.AlarmSubscribe, AlarmSubscriptions and the TAPI
notification intake all answered correctly against the live controller.mvn package, BUILD SUCCESS) and the
forwarding methods are present in the packaged classes.This work is funded by the European Commission through the HORIZON-JU-SNS-2023 PROTEUS-6G project with Grant Agreement number 101139134.
File added.
Preview size limit exceeded, changes collapsed.