Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Interfaces incorrectly marked as having flows resulting in no data via Helm

Description

The logic for flows coming into the system need to be re-evaluated. The current method is marking interfaces as having flows resulting in a list of interfaces in Helm that return no data. This leads to confusion from a user perspective.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Patrick Schweizer September 24, 2020 at 12:52 PM

Patrick Schweizer September 11, 2020 at 5:19 PM
Edited

General notes on how the mechanics work:

Writing
ElasticFlowRepository.persist() line 270

Reading

List of interfaces with flows:
org.opennms.netmgt.flows.rest.FlowRestService.getFlowExporters and getFlowExporter

Reading of flow data from interfaces that might turn out empty:

ElasticFlowRepository.getHostSeries()

Fixed

Details

Assignee

Reporter

Labels

HB Backlog Status

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created July 20, 2020 at 1:00 AM
Updated October 14, 2020 at 4:33 PM
Resolved September 24, 2020 at 12:53 PM