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

Metrics and dashboard enhancements for Lokiless usage

    • Icon: Epic Epic
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • netobserv-1.5
    • None
    • None
    • networking-state-dashboards-1.5
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-964 - Metrics and dashboard enhancements for Lokiless usage
    • OCPSTRAT-964Metrics and dashboard enhancements for Lokiless usage
    • 0% To Do, 0% In Progress, 100% Done
    • L

      Epic Goal

      • Add PktDrop, DNS, RTT metrics
      • Add Resource (Pod / Service) metrics
      • Ensure users understand the performance impacts
      • Document these impacts

      Why is this important?

      Since 1.4 release, netobserv allow installation without Loki. To keep the ability to drill down into DNS & PktDrop, we should expose these in Prometheus metrics.

      It's also a good opportunity to add the RTT ones that will be supported in 1.5 and update the flow dashboards accordingly.

      Before exposing metrics that can kill the cluster performances, we should ensure it is explicitly requested in the CR and the user understand the impact.

      Planning Done Checklist

      The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

      • Priority+ is set by engineering
      • Epic must be Linked to a +Parent Feature
      • Target version+ must be set
      • Assignee+ must be set
      • (Enhancement Proposal is Implementable
      • (No outstanding questions about major work breakdown
      • (Are all Stakeholders known? Have they all been notified about this item?
      • Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)

      Additional information on each of the above items can be found here: Networking Definition of Planned

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement
        details and documents.


      Dependencies (internal and external)

      Followup on:





            jtakvori Joel Takvorian
            jpinsonn@redhat.com Julien Pinsonneau
            Amogh Rameshappa Devapura Amogh Rameshappa Devapura
            0 Vote for this issue
            6 Start watching this issue