Autonomous Alarm Purge based on retention period 51/13851/7
authorZhang Rong(Jon) <rong.zhang@windriver.com>
Thu, 12 Dec 2024 09:44:25 +0000 (17:44 +0800)
committerZhang Rong(Jon) <rong.zhang@windriver.com>
Thu, 16 Jan 2025 15:35:30 +0000 (23:35 +0800)
commit935ccb8b8220b33dc30449bc6a1e901d12da98cb
treef36fcbdb71cf313ea2423e0b9ec2f2bba3c348bf
parent6b65f83f4a115da4c066d4aca91d1d78fbc00d37
Autonomous Alarm Purge based on retention period

This commit introduces an autonomous purge mechanism for alarm event
records based on the retention period specified in the alarm service
configuration.

Previously, the "purge event" was used for clearing alarms. To improve
clarity, the "clear" and "purge" events have been split to better
distinguish their respective purposes.

Test Plan:
PASS - Successfully purges alarm event records that exceed the retention
       period.
PASS - Ensures that alarm event records not in "clear" or "acknowledged"
       status remain unaffected.
PASS - Verifies that clearing an alarm operates as expected.

Change-Id: I2414caa4929daf3efb1ccb9848f84ef69b80318f
Signed-off-by: Zhang Rong(Jon) <rong.zhang@windriver.com>
14 files changed:
o2app/entrypoints/redis_eventconsumer.py
o2app/service/handlers.py
o2ims/adapter/alarm_repository.py
o2ims/adapter/clients/fault_client.py
o2ims/adapter/orm.py
o2ims/domain/alarm_obj.py
o2ims/domain/commands.py
o2ims/domain/events.py
o2ims/service/command/clear_alarm_handler.py [new file with mode: 0644]
o2ims/service/command/purge_alarm_handler.py
o2ims/service/event/alarm_event.py
o2ims/service/watcher/alarm_watcher.py
o2ims/views/alarm_route.py
o2ims/views/alarm_view.py