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

Nephron: Get rid of convo_key and grouped_by_key

    XMLWordPrintable

Details

    • Enhancement
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • 29.0.0
    • None
    • Security Level: Default (Default Security Scheme)
    • None
    • 3
    • Horizon 2021 - Oct 28 - Nov 10
    • Backlog CM

    Description

      This ticket may improve Nephron performance slightly.

      The information contained in the convo_key is also available in separate fields. Nephron already relies on these fields when calculating its aggregations.

      Convo-Key can be removed from

      •  the flow proto-bufs (raw & summary)
      • from ES raw flows (needs check if ES can aggregate based on several fields)
      • from ES summary flows

      When the convo_key is removed from ES then backwards compatibility must be considered. ATM OpenNMS relies on that field because it extracts parts from the string.

      In addition, the grouped_by_key of flow summaries also does only contain information that is available in separate fields. It also seems not to be used anywhere.

      Attachments

        Issue Links

          Activity

            People

              swachter Stefan Wachter
              swachter Stefan Wachter
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.