-  Supressor - New AoM field to declare dependencies' alerts - if any in dependencies' alerts are firing, then do not check
   x  AoM is not AoM - it's just configurations
      -  Each AoM is a process dedicated to looping over 1 alert
      -  Kills & recreates processes on config change (?)
      -  Oh my god monolithic functions
      -  Insert suppress at comment "send all alerts found to the alert handlers..."
      -  No unittests
      -  Seems no multiplicity
      -  serviceapp/service.py
   -  Floyd-Warshall create fully connected graph on boot/MR as CSV
-  Reporter - Slack bot to get graph/latest check by name
   -  Lookup AoM configs in Gitlab - fetch all on interval with PAT
      -  configs stored in docker image
      -  seem to be reloadable on MRs
   -  Execute query and return
      -  See nexpose for prometheus, kairos API
      -  matplotlob.pyplot
      -  last N values
      -  warning threshold
      -  critical threshold
-  Visualizer - New AoM field to declare service name and dependent services' names - visible map of services as alerts firing and links between
   -  Hit uchiwa API for what's firing? How to handle silenced?
   -  Does AoM have an API for what's firing?