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

Some AM 5.5 Call Home metrics no longer reported by AM 6.0

    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:
    • Target Version/s:
    • 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

      Some of the Call Home metrics reported by AM 5.5 have been renamed in AM 6.0 and org.forgerock.openam.backstage.CrestMetricSupplier has not been updated to reflect these changes. This means that renamed metrics will not be collected and reported by the CrestMetricSupplier.

      How to reproduce the issue

      Launch an evaluation version of AM 6.0.0 and observe the metrics collected by the CrestMetricSupplier (the simplest way to achieve this may be by using a debugger).

      Expected behaviour
      CrestMetricSupplier collects the following metrics:
      * authentication.success
      * authentication.failure
      * authentication.timeout
      * authentication.unique-uuid.success
      * authentication.module.<module-name>.success
      * authentication.module.<module-name>.failure
      * authorization.policy-set.<policy-set-name>.evaluate.success
      * authorization.policy-set.<policy-set-name>.evaluate.advice.<advice-type-name>
      * oauth2.grant.issue
      * oauth2.authorization-code.issue
      * oauth2.access-token.issue
      * oauth2.refresh-token.issue
      * oauth2.device-code.issue
      * oauth2.open-id-connect.id-token.issue
      * oauth2.open-id-connect.ops.issue
      * session.cts.create.success
      * session.stateless.create.success
      
      Current behaviour
      CrestMetricSupplier fails to collect the following metrics as they have been renamed:
      * oauth2.grant.issue
      * oauth2.authorization-code.issue
      * oauth2.access-token.issue
      * oauth2.refresh-token.issue
      * oauth2.device-code.issue
      * oauth2.open-id-connect.id-token.issue
      * oauth2.open-id-connect.ops.issue
      * session.cts.create.success
      * session.stateless.create.success
      

      Work around

      N/A

      Code analysis

      CrestMetricSupplier filters should be updated to collect the following renamed metrics:

      • oauth2.grant.issue --> oauth2.grant.<grant-type>
      • oauth2.authorization-code.issue --> oauth2.token.authorization-code.issue
      • oauth2.access-token.issue --> oauth2.token.access-token.issue
      • oauth2.refresh-token.issue --> oauth2.token.refresh-token.issue
      • oauth2.device-code.issue --> oauth2.token.device-code.issue
      • oauth2.open-id-connect.id-token.issue --> oauth2.token.id-token.issue
      • oauth2.open-id-connect.ops.issue --> oauth2.token.ops.issue
      • session.cts.create.success --> session.cts-based.create.success
      • session.stateless.create.success --> session.client-based.create.success

        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: