Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-11862

Root Cause Indication

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: ALEC
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Epic Name:
      Root Cause

      Description

      This is a user story that has implications across multiple projects: Horizon/Meridian, Helm, and OCE.

      When a situation is created, the OCE should identify the root cause (RC) Alarm and provide indication to the user. The methodology of identifying the RC should be based on the following criteria:

      1. User feedback
      2. RC weight value (0-100) in alarm-data configuration
      3. Timing
      4. Model

      Example for user feedback/ML training: User should be able to adjust RC identification for a particular situation via a check box next to the list of "Alarms in Situation".

      Example of weighting of alarms, users should be able to provide a weight to particular Alarms in the alarm-data configuration element. Alarms that are likely to have higher weights are configuration change alarms and transmission layer alarms.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            david David Hustace
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: