Uploaded image for project: 'Architecture for Learning Enabled Correlation (ALEC)'
  1. Architecture for Learning Enabled Correlation (ALEC)
  2. ALEC-131

Configuration Page where ALEC Engine is selected



    • Story
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • None
    • None


      As Neil, the IT Engineer and the person in charge of deciding how to manage the network, I want an easy way to understand the benefits of different correlation mechanisms and need to choose the best one for my organization so that the situations identified to reduce Mean Time to Repair (MTTR) and similar metrics.

      In the future, we will allow fine-tuning of the engines and use different engines for different groups of devices.

      At this time, we just need to provide two options:  Either use DBSCAN or use DBSCAN with Hellinger Distance.

      Check ALEC Definitions document.  If DBSCAN / Hellinger are not described there, ask Gerardo to do so.

      Acceptance Criteria:

      • By default, the system ships with DBSCAN as the Engine.
      • When a user with ROLE_ADMIN logs in for the first time, the user is given:
        • Description of each engine.
        • A choice of engine.
      • Choice of the engine is recorded, along with the date it was recorded.  This date will be needed in the future for when we can provide new/better choices for the user.

      What is not needed (Yet):

      • This story works with or without the engine selection taking effect.  (At least it doesn't break the code).
      • The engine can be changed on a new Admin page (gear-shaped top right).
      • Upon availability of a new engine (after an upgrade), the ROLE_ADMIN user is given the choice of selecting a different Engine.  The old engine selection is preserved until the ROLE_ADMIN user selects a new one (if they select it).




            Anya Rybalova Ganna Rybalova
            joseanes Jose
            0 Vote for this issue
            1 Start watching this issue