Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-1131

Metrics do not ignore duplicates

    • False
    • None
    • False
    • Hide
      Previously, the Prometheus metrics exported by Network Observability were computed out of potentially duplicated network flows. In the related dashboards (from menu "Observe" > "Dashboards"; note that dashboards from the "Network Traffic" page were not affected), this could result in potentially doubled rates.

      Now, network flows are filtered to eliminate duplicates prior to metrics calculation, which results in correct traffic rates displayed in the dashboards.
      Show
      Previously, the Prometheus metrics exported by Network Observability were computed out of potentially duplicated network flows. In the related dashboards (from menu "Observe" > "Dashboards"; note that dashboards from the "Network Traffic" page were not affected), this could result in potentially doubled rates. Now, network flows are filtered to eliminate duplicates prior to metrics calculation, which results in correct traffic rates displayed in the dashboards.
    • NetObserv - Sprint 238

      Note I haven't tested, just figured out looking at the metric definitions, such as https://github.com/netobserv/network-observability-operator/blob/main/controllers/flowlogspipeline/metrics_definitions/node_egress_bytes_total.yaml

      There's currently no filter for Duplicate=false, which I think means the produced values are ~doubling the actual byte rates. We should confirm this by comparing rates between our console plugin (which filters for duplicates) and these dashboards.

      Note that the fix would involve improving the FLP API, since it seems only able to apply a single filter.

      [Edit: discrepancy confirmed, cf attached screenshots]

            jtakvori Joel Takvorian
            jtakvori Joel Takvorian
            Mehul Modi Mehul Modi
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: