Uploaded image for project: 'Cluster Observability Operator'
  1. Cluster Observability Operator
  2. COO-319

Bubble size on Scatter plot graph is not rendered correctly for Distributed Tracing UI Plugin

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • 1.0.0
    • 0.4.0
    • tracing-uiplugin
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Previously...When we view a Tempo instance from the Distributed Tracing UI plugin, the scatter plot graph showing the traces duration is not rendered correctly. The bubble size is too large and overlaps the x and y axis...

      With this release...the graph is rendered correctly...
      Show
      Previously...When we view a Tempo instance from the Distributed Tracing UI plugin, the scatter plot graph showing the traces duration is not rendered correctly. The bubble size is too large and overlaps the x and y axis... With this release...the graph is rendered correctly...
    • Bug Fix
    • In Progress
    • None

      Version of components:

      cluster-observability-operator.0.4.0
      OCP version 4.16.0-0.nightly-2024-09-02-173242
      Google Chrome Version 128.0.6613.86 (Official Build) (arm64) on Mac M2

      Description of the issue:
      When we view a Tempo instance from the Distributed Tracing UI plugin, the scatter plot graph showing the traces duration is not rendered correctly. The bubble size is too large and overlaps the x and y axis. 

      Steps to reproduce the issue:

      *Install the COO 0.4.0 operator.

      *Create the Tracing UI plugin instance with the following CR.

      apiVersion: observability.openshift.io/v1alpha1
      kind: UIPlugin
      metadata:
        name: distributed-tracing
        namespace: openshift-operators
      spec:
        type: DistributedTracing
      

      *Deploy a TempoStack instance with multiteanancy enabled, generate and send traces to the instance. 

      git clone git@github.com:openshift/distributed-tracing-qe.git
      go install github.com/kyverno/chainsaw@latest
      cd distributed-tracing-qe
      chainsaw test --skip-delete tests/e2e-acceptance/multitenancy
      or 
      Create the resource file skipping the assert ones one by one following the file index. 

      *Check the TempoStack instance from the Tracing UI. The bubble size on the scatter plot graph will be large and overlapping the axis. 

       

            [COO-319] Bubble size on Scatter plot graph is not rendered correctly for Distributed Tracing UI Plugin

            This issue was resolved in COO 1.0, so closing it out. 

            Ishwar Kanse added a comment - This issue was resolved in COO 1.0, so closing it out. 

            Verified fix in 

            observability-operator.v0.4.3-241106161705 

            Ishwar Kanse added a comment - Verified fix in  observability-operator.v0.4.3-241106161705 

            The current logic is to compute the maximum duration of all found traces, and scale the bubble sizes accordingly.
            If all traces in the search result have the same duration, the maximum bubble size is taken (which is currently set to 80px).

            In upstream I already fixed this to make the maximum bubble size much smaller (20px diameter, same as the Jaeger UI)
            PR: https://github.com/perses/perses/pull/2197
            Will land in next COO version.

            Andreas Gerstmayr added a comment - The current logic is to compute the maximum duration of all found traces, and scale the bubble sizes accordingly. If all traces in the search result have the same duration, the maximum bubble size is taken (which is currently set to 80px). In upstream I already fixed this to make the maximum bubble size much smaller (20px diameter, same as the Jaeger UI) PR: https://github.com/perses/perses/pull/2197 Will land in next COO version.

              agerstma@redhat.com Andreas Gerstmayr
              rhn-support-ikanse Ishwar Kanse
              Ishwar Kanse Ishwar Kanse
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: