Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-552

Fix the spikiness in the data studio disruption graphs

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • False
    • None
    • False

      https://datastudio.google.com/reporting/26007bde-88c8-44dd-8fb9-4f5e41dfb0ce/page/p_i6fa5cr1mc

      These are effectively useless, alternating between 5s one day and 1400 the next.

      We should switch to using a rolling average perhaps over 7 days similar to sippy. Possible a sql technique could work like: https://learnsql.com/blog/rolling-average-in-sql/

      The y axis also needs to go well beyond 100 somehow, azure is out of control. It's possible these values will drop in half when https://github.com/openshift/origin/pull/27415 merges.

            rhn-engineering-dgoodwin Devan Goodwin
            rhn-engineering-dgoodwin Devan Goodwin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: