Uploaded image for project: 'Network Controller'
  1. Network Controller
  2. SDNC-616

SDN-R WT app need to change alarm severity "Configurable" for ConnectionLossxxx alarm family (received from Mediator) , when it passed to DCAE VES collector

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • Dublin Release
    • Dublin Release
    • sdnc-apps
    • SDNC Dublin Spr 3 3/11 - 3/29

      SDN-R WT app need to change alarm severity configurable (like Major, CRITICAL, MINOR, etc) for ConnectionLossxxx alarm family (received from Mediator) , when it passed to DCAE VES collector. Currently severity is set to "Major"

       

      Severity of following alarms in the ONAP Code may change from "MAJOR" to CRITICAL. Currently DCAE VES Collector is receiving it as a MAJOR alert for below "alarmCondition"

                      "alarmCondition": "ConnectionlossNeOAM"

                      "alarmCondition": "ConnectionlossOAM"

                      "alarmCondition": "ConnectionlossMediator"

       

      This needs to be configurable for "alarmCondition".

      Martin Skorupski from HighStreet pointed the places in Dublin release the severity of SDN-R deviceMonitoring alarms is hard-coded - see code line 36, 42, 47

      https://github.com/onap-oof-pci-poc/ccsdk/blob/master/features/sdnr/wt/devicemanager/provider/src/main/java/org/onap/ccsdk/features/sdnr/wt/devicemanager/devicemonitor/impl/DeviceMonitorProblems.java

       

      Solution Implementation:

      • add property to device manager config file
      • default: major "alarmCondition": "ConnectionlossNeOAM"

       "alarmCondition": "ConnectionlossOAM"

       "alarmCondition": "ConnectionlossMediator"

            highstreetherbert Herbert Eiselt
            payamfor payamfor
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: