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

Unique User Login Count metric not working

    Details

    • Needs backport:
      No
    • Needs QA verification:
      No
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      Yes and I used the same an in the description

      Description

      Bug description

      The following DropWizard metric is not counting the number of unique users logging in:

      • authentication.unique-uuid.success

      How to reproduce the issue

      1. Select Configure > Global Services > Monitoring
      2. Ensure "Monitoring Status" and "Monitoring RMI interface status" are both checked
      3. Connect to OpenAM via JMX (e.g. using jconsole)
      4. Expand the org.forgerock.openam folder and select the authentication.unique-uuid.success metric
      5. Login to OpenAM using a number of different user accounts
      6. Refresh the authentication.unique-uuid.success metric
      Expected behaviour
      The authentication.unique-uuid.success metric should estimate the number of different users who have logged in - With at most +/- 1% error.
      
      Current behaviour
      The authentication.unique-uuid.success metric always reports 2 unique user logins.
      

      Work around

      N/A

      Code analysis

      It's not clear why this should be the case. The unit tests for org.forgerock.openam.monitoring.DistinctCounter suggest we should be able to get within 1% margin or error while only using 80KB of memory. Stepping through the calls to com.sun.identity.authentication.service.AMLoginContext#authenticationSuccessUniqueUuidMetric in the debugger makes it look like everything is wired up correctly. Further debugging necessary.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: