Set the fixed version to "Next" because the issue is a Helm issue and OpenNMS versions do not apply.

PR: https://github.com/OpenNMS/opennms-helm/pull/312

The existing ES-based "Flow Deep Dive Dashboard" uses as the initial sort order for the "Data Usage by Application/Host/DSCP" tables the sum of ingress+egress. In order to achieve the same initial ordering an additional "hidden" column is used. Unfortunately that column may become visible if a user scrolls these tables.

Alternatives would be

• Do not hide the sum column at all

• Use either ingress or egress as the initial sort order

In order to review the "Cortex Flow Deep Dive Dashboard" a Cortex installation filled with flow aggregation data must be available.

First, checkout Nephron's branch jira/NMS-13374-data-for-review.

While in the root directory of Nephron, Cortex can be started in a Docker container executing:

Data is persisted inside the container, i.e. no cleanup is necessary later on.

Nephron's benchmark application can be used to persist flow aggregation data in Cortex. While in the root directory of Nephron, the benchmark application can be run by:

The benchmark argument file generate-review-data.arg configures the benchmark application such that a local Cortex installation and an embedded Flink cluster is used. The benchmark application should run a little more than 300 seconds producing 30 windows of flow data each window covering 10 seconds.

It was decided to include the dashboard in the helm plugin.