Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-13029

Prometheus Dashboards timer panels showing incorrect units

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.0.0
    • Fix Version/s: 6.0.0
    • Component/s: monitoring
    • Labels:
      None
    • Needs backport:
      No
    • Needs QA verification:
      No
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      No (add reasons in the comment)

      Description

      Bug description

      The demo Grafana dashboards using Prometheus data are configured to interpret timing metrics as provided in milliseconds. This is incorrect as Prometheus provides these values as seconds. This means that these graphs are showing timing metrics with values 1000x too small.

      How to reproduce the issue

      1. Enable collection of monitoring via Prometheus and setup a Prometheus server as described here
      2. Load the demo dashboards (described by the same README linked to above)
      3. Interact with AM and observe the dashboards
      Expected behaviour
      CTS operations should be recorded as taking in the region of 1-50 milliseconds for an AM server under light load.
      
      Current behaviour
      CTS operations are reported to take in the region of 0.001-0.050 milliseconds.
      

      Work around

      N/A. The Grafana dashboard configurations need to be updated and a new export committed to AM.

      Code analysis

      N/A

        Attachments

          Activity

            People

            • Assignee:
              craig.mcdonnell Craig McDonnell
              Reporter:
              craig.mcdonnell Craig McDonnell
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: