Currently the admin GUI just logs and ignores notifications about Alarms with names that do not match any alarm name in the Alarms (registration) cache:
We should probably make these notifications available to users on the interface somehow. Perhaps:
Insert a new Alarm registration dynamically. This is problematic because currently there are many required fields we won't have values for. We could create "UNKNOWN" placeholders in the ACTION, COMPONENT, and TEAM columns, but that sorta defeats the whole purpose of defining constraints. Perhaps make the fields nullabe?
Dump the records into a separate "dead letter queue". This has some management cost. Maybe a circular queue? Users would need to know to look in the queue periodically.
slominskir
commented
4 months ago
Currently the admin GUI just logs and ignores notifications about Alarms with names that do not match any alarm name in the Alarms (registration) cache:
https://github.com/JeffersonLab/jaws-admin-gui/blob/39eecd8f56b4ce4877f386fecd6937ca0f2a8c0f/src/main/java/org/jlab/jaws/business/session/KafkaNotificationFacade.java#L64
We should probably make these notifications available to users on the interface somehow. Perhaps: