Uploaded image for project: 'Logging analytics'
  1. Logging analytics
  2. LOG-964

Enhance POMBA validator to permit a given rule to return more than one result

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Medium Medium
    • None
    • None
    • POMBA Multiple Results per Rule

      As a POMBA user, I would like a rule to be able to process all the fields covered by that rule in one shot rather than one at a time (i.e., exiting the rule at the first violation).  Having this capability will make audits more useful, as a user wouldn't have to hit their violations in sequence by doing multiple audits.

      If I understand correctly, the issue preventing this was one of how to report out on more than one violation.  A suggestion is to return a list of violations from each rule and use templated error strings.

      For example, let's say we have fields vnf-name and orchestration-status in a VNF and we are comparing AAI and SDNC.

      Currently, I believe a mismatch in the two vnf-names would cause the rule to stop and a violation to be returned and orchestration-status would not be checked.

      The violation text itself is non-templated, meaning I cannot paste in identifier information into it.  For example, here is text of a current violation string:

      VNF Name in AAI does not match VNF Name in SDN-C object record

      Alternatively, the text could be:

      %s %s in %s does not match %s %s in %s for entity type %s with identifier %s

      {vnf-name, aainame, AAI, vnf-name, sdncname, SDNC, vnf, vnfid}

      would be the data set used to populate the template the first time, then

      {orchestration-status, aaiostatus, AAI, orchestration-status, sdncostatus, SDNC, vnf, vnfid}

      is used the 2nd time.

       

       

       

            Unassigned Unassigned
            ccwechsler ccwechsler
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: