[GLASSFISH-17172] Improving Monitoring Tree Created: 09/Aug/11  Updated: 09/Aug/11

Status: Open
Project: glassfish
Component/s: monitoring
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Jennifer Chou Assignee: Byron Nevins
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Investigate improving monitoring tree for stability (There were many regressions in 3.1).

Potentially refactor AbstractTreeNode:

  • Remove if possible "band-aid" fixes:
  • encoding/decoding
  • Better way to do pattern matching?
  • Currently, in getNodes(String pattern) the dotted name pattern is converted to regex. Code goes through the entire list of tree nodes and compares the pattern with the complete dotted name of the nodes to find the list of matching TreeNodes.

Notes:

  • A TreeNode consists of node name and whether the node is enabled. The TreeNode can also contain a method on an instance to invoke to return a Statistic object.
  • asadmin get -m (MonitoringReporter) and REST (MonitoringResource) both use the monitoring tree to display the statistics. REST uses getNode (String completeName) and get -m command uses getNodes(String pattern). REST monitoring does not take '*' wildcard like the get -m command can use. That's why they use different path to retrieve the statistics.

Generated at Sat Oct 01 03:47:27 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.