Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-1104

Visualize results of SBO Performance Test

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • QE, Service Binding
    • None
    • Visualize SBO Performance
    • False
    • False
    • 0% To Do, 0% In Progress, 100% Done

      Problem:

      Currently the SBO performance test generates a set of CSV files for the resource utilization (CPU, Memory throughout the duration of the test) for various Kubernetes resources including SBO pod itself as well as the computed performance metrics such as TimeToReconcile, ReconciledToDone or TimeToDone for each of the testing scenarios. The KPI (key performance indicators) are also computed (as various aggregated statistical values such as average, median, minimal, maximal, etc.) for each of the performance metrics and testing scenarios.

      Keeping the results in the form of CSV files is good for machine processing), however is not easy to read for humans. We need to visualize those results and metrics in a graphical form (such as charts)

      Goal:

      Be able to see and share the results of the SBO performance test presented in a visualized form.

      Why is it important?

      Use cases

      • Performance testing jobs such as PR checks or SBO downstream release testing jobs are able to upload/import the result data into Segment
      • Users are able to show a dashboard with results for a chosen performance test run

      Demo requirements

      Acceptance criteria

      Development:

      • Segment with Woopra is setup for storing and presenting SBO KPI metrics
      • A tool capable of importing KPI of SBO Performance test is used
      • Metrics for average and maximum values of KPIs (CPU and Memory usage) is defined
      • Woopra dashboards are created to visualize the KPI metrics
      • A public link to the dashboard for the current performance test run is available

      QE:
      Documentation: Yes/No (needs-docs|upstream-docs / no-doc)

      Upstream: <Inputs/Requirement details: Concept/Procedure>/ Not
      Applicable

      Downstream: <Inputs/Requirement details: Concept/Procedure>/ Not
      Applicable

      Dependencies (External/Internal)

      Design Artifacts

      Exploration

      Note

              Unassigned Unassigned
              pmacik@redhat.com Pavel Macik
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: