-
Epic
-
Resolution: Done
-
Highest
-
None
-
Formal alarm handling from xApps and from RICplatform, excluding actual alarms
Note that as of May-7 we only have a go library for rasing alarms, C++ and python we don't have. First one needing it could implement this library based on the go example.
We might change the title once we have the health check use case clarified
Note that xApps might report alarms using RMR (to avoid a sidecar solution).
Includes:
xApp can raise/clear alarm
platform components can raise/clear alarm
new component that manages alarms - ideally re-using Prometheus alert manager, but keep solution in a way that other alarm managers could be used.
O1 mediator makes list of active alarms visible via netconf and VES events sent for alarm changes.
To be defined some platform alarms
Send a heartbeat alarm/notification via VES
By early february we should have a list (by name) of alarms we want to work on in Bronze. Thsi list is to be sent to Martin Sko... (highstreet). We now have RIC-585, RIC-203, RIC-204 as candidates, but all are stretch goals for Bronze.
Note one option is that the alarm library (to be used by xApps and platform compornents) can be controlled by an environment variable to (a) send alarm structure via RMR or (b) send a log to stdout).
- mentioned in
-
Page Loading...