[OPENAM-12160] CTS connection metrics should not be updated by UMA Created: 30/Nov/17  Updated: 26/Mar/18

Status: Open
Project: OpenAM
Component/s: CTS, monitoring, UMA
Affects Version/s: 5.5.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Craig McDonnell Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
Epic Link: Replace In-House Monitoring Framework with DropWizard Metrics (phase 3)

 Description   

Bug description

The metrics cts.connection.success and cts.connection.failure are updated by both CTS and UMA operations. However, while UMA uses the same "data layer" APIs as CTS, UMA is not a consumer of CTS and therefore should have its own metrics for tracking connections to DJ.

How to reproduce the issue

Details steps outlining how to recreate the issue (remove this text)

  1. Enable JMX monitoring
  2. Complete an UMA flow
  3. Observe updates to the cts.connection.success metric (via JMX, e.g. using JConsole)
Expected behaviour
cts.connection.success is only updated for operations going through CTS
Current behaviour
cts.connection.success is also updated for operations going through UMA

Work around

N/A

Code analysis

See PR for AME-14233


Generated at Tue Nov 24 00:32:10 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.