JMX monitoring
In the java world, it is very common to use JMX as supervision and monitoring technology.
As JMX is a standard and is supported by most supervision tools, the chtijbug library implements two mbeans.
Rule Base Mbean
Our current implementation is minimal. It allows to get a list of the used ressources by their names, to query if the knowledge base is loaded allows to rebuild the knowledge base. This is very useful if you want to reload rules from a Guvnor repository.
A lot of improvements are needed : DROOLS-9 - Getting issue details... STATUS
The name of this mbean is
org.chtijbug.drools.runtime:type=RuleBaseSupervision
State-full Session MBEAN
This mbeans gives information on all sessions attached to the RuleBase.
the name if the mbean is
org.chtijbug.drools.runtime:type=StateFullSessionSupervision
Some enhancements are needed for that part : DROOLS-10 - Getting issue details... STATUS
| getAverageTimeExecution | Average fireAllRules time execution |
|---|---|
| getMinTimeExecution | Minimum fireAllRules time execution |
| getMaxTimeExecution | Maximum fireAllRules time execution |
| getAverageRulesExecuted | Average number of rules fired during a fireAllRules |
| getMinRulesExecuted | minumum number of rules fired during a fireAllRules |
| getMaxRulesExecuted | Maximum number of rules fired during a fireAllRules |
| getAverageRuleThroughout | Average number of rules executed per second during a fireAllRules |
| getMinRuleThroughout | minimum number of rules executed per second during a fireAllRules |
| getMaxRuleThroughout | Maximum number of rules executed per second during a fireAllRules |
| resetStatistics | Reset all previous statistic |
| isGenerateXMLHistoryContainer | if true, then the HistoryContainer of the session is sent in the JMX event generated for each fireAllRules Commands Is set to false by default |
| setGenerateXMLHistoryContainer | Set/unset the generation of the HistoryContainer |
UML diagram
