...
- Ontological alignment. Our “Alarms” and Argus “Incidents” are slightly different, so we need to explore the consequences of this (e.g. we want “Alarms” to be displayed that don’t have incident tickets in the ticketing system)
- Django requires internal technical expertise or even ‘Django devs’
- Lack of Alarm states (our “phases”)
- Absence of alarm history or searchability.
- Only one line of acknowledgment (We have first and second line requirements)
- Inability to drill down into issues.
- No blacklists.
- Filtering not as comprehensive.
- Won’t naturally coalesce or correlate (integrations required).
- Flapping not addressed (for future consideration).
- Prioritisation not handled.
...
- Desired Future State: That alarms can have states. For example flashing if new. Or different colours to say whether they are pending or urgent.
- Gap: The current inability of Argus to support multiple alarm states (e.g. flashing for new, different colours for pending/urgent) poses a functional gap when compared to the desired future state. The absence of such features hinders the support teams ability to react quickly to distinguish or respond to the different alarm conditions, leading to a potential delay in addressing critical issues. This could have an impact on operations and UX.
Feature/Functionality: Multiple stages of Acknowledgment
⁃ Current State (System A): Dashboard currently demands that both differentiates between 1st and 2nd line support teams to acknowledge acknowledgement that Alerts have been recognised recognised
⁃ Current State (System B): Alarms only have 1 level of acknowledgement. ( ‘Acked’ is a tag or status )
- Desired Future State: That Alarms have 2 levels of acknowledgement
- Gap: The current inability of Argus to support multiple teams poses a problem and is a functional gap. 2nd line support don’t need to be wasting their time on issues that have already been investigated by first line of support. Or similarly do need to know whether 1st line has addressed a given issues with in the time set by the SLA.
Feature/Functionality: Correlation and Coalescing
⁃ Current State (System A): Supports coalescing and correlating issues for remediation.
⁃ Current State (System B): Lacks the ability to coalesce and correlate alerts effectively.
...