Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SMILA/Project Concepts/Generic Management And Monitoring Concept"
Line 13: | Line 13: | ||
− | === Performance Counters Module Architecture | + | === Performance Counters Module Architecture === |
See [[SMILA/Project_Concepts/Performance_counters_API|Performance Counters API]] | See [[SMILA/Project_Concepts/Performance_counters_API|Performance Counters API]] | ||
− | + | === Management Module Architecture === | |
− | + | ||
− | + | ||
− | + | ||
− | === Management Module Architecture | + | |
This chart shows the Management architecture: | This chart shows the Management architecture: | ||
Line 27: | Line 23: | ||
[[Image:ManagementRegistry.png]] | [[Image:ManagementRegistry.png]] | ||
//TODO | //TODO | ||
+ | |||
+ | |||
+ | === Performance Counters Module Architecture issues=== | ||
+ | |||
+ | * its impossible to group counters into tree legally by API ( now its used "JMX specific names" hack to group them ) | ||
+ | * its impossible to have few counters nested in one JMX leaf | ||
+ | * its impossible to predict when counter will be initialized to start tracking because it initialized only on first usage | ||
+ | |||
+ | === Management Module Architecture issues === | ||
* its impossible to group agents into tree | * its impossible to group agents into tree | ||
− | === Common | + | === Common issues === |
* its impossible to mix performance counters and management agents methods nested in one JMX leaf | * its impossible to mix performance counters and management agents methods nested in one JMX leaf | ||
Line 54: | Line 59: | ||
</source> | </source> | ||
− | But its also possible (and suggested) to separate them because dependencies. | + | But its also possible (and suggested) to separate them because dependencies. Mainly Management Agent using service and not used inside the service. And is visa versa for Counters Agent |
− | Mainly Management Agent using service and not used inside the service. And is visa versa for Counters Agent | + | |
<source lang="java"> | <source lang="java"> |
Revision as of 12:38, 3 March 2009
Contents
Description
Now SMILA uses separate modules for Management and for Performance Counters but both uses JMX (jconsole) as a default presentation layer.
During other components development it was found that both modules have issues.
This page is a concept about merging both modules into one generic module and to avoid issues found.
Discussion
Technical proposal
Performance Counters Module Architecture
Management Module Architecture
This chart shows the Management architecture:
Performance Counters Module Architecture issues
- its impossible to group counters into tree legally by API ( now its used "JMX specific names" hack to group them )
- its impossible to have few counters nested in one JMX leaf
- its impossible to predict when counter will be initialized to start tracking because it initialized only on first usage
Management Module Architecture issues
- its impossible to group agents into tree
Common issues
- its impossible to mix performance counters and management agents methods nested in one JMX leaf
Proposal
Its suggested to use one registry from management module ( its more generic ) to use operations and counters.
Description and initialization of performance counters will be in the Management Agent implementation. It will allow to group counters (also together with management operations).
class MyAgent implements Agent{ // some management operation public doSomething(args[]); // some performance counter related to that module public PerformanceCounter getCounterOne(); // other performance counter related to that module public PerformanceCounter getCounterTwo(); }
But its also possible (and suggested) to separate them because dependencies. Mainly Management Agent using service and not used inside the service. And is visa versa for Counters Agent
class MyManagementAgent implements Agent{ ... public doSomething(args[]); .... } class MyCountersAgent implements Agent{ public PerformanceCounter getCounterOne(); public PerformanceCounter getCounterTwo(); }