• Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 6.5.0, 6.5.1, 6.5.2,,
    • Fix Version/s: None
    • Component/s: monitoring
    • Labels:
    • Support Ticket IDs:


      Problem: The current metrics on AM seems to be based on

      am_authentication [13]
      am_blacklist [63]
      am_cts_connection [16]
      am_reaper [17]
      am_cts_task [1577]
      am_jvm [75]
      am_oauth2_grant [18]
      am_oauth2_token [32]
      am_session [1348]

      with the metrics on the type of CTS, in-memory, etc.  However, it does not offer metrics on the API endpoint being called. For example, the metric like how many session validation calls have been called from the REST endpoint cannot be inferred. The reason is that all the above metrics say session.<session-type>.validate.<outcome> are the internal backed calls.

      In fact the even if the REST call say for /json/session?_action=validate is called once, the metric for session.cts-based.validate.success jumps more that 8-10. The reason being the front-end REST endpoint does call into the internal validation many times (maybe indicating there may be better optimization ). We still do not have the direct metric for the number of times the call as a metrics (not like we should be scraping access logs for these information !!!)



      1. Metrics for the frontend REST endpoint (like what you would get directly thru the access logs for these) (thing related to this includes session validate, session get/set properties,







          Issue Links



              • Assignee:
                chee-weng.chea C-Weng C
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created: