@ll, I have a question regarding the possibilities to monitor and report on the rules activity. I have seen that with Drools Guvnor, it is perfectly possible to monitor scenario's, see what rules fired, etc. Now, going further, I have two questions: - Is it possible to monitor rule activity (which rules got fired etc) in a production situation. Eg. Is it possible to start recording activity at some time until a proble occured and to review the logs afterwards. This would be of use when scenario's are not covering all possible cases. - Is it possible to produce reports on rules, usage of rules (eg. what rules are fired and what rules were fired most), performance, ... And if not, what could be a good starting point to create them ? My experience with Drools is rather limited. Let's say that I am interested in expert system and technologies surrounding it. At this moment I am getting a 'theoretical' grip on Drools and its possibilities (of course, I couldn't help also creating some kind of poc :) ). Sincerely, Dieter D'haeyere. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

wrote:

It seems to be hard to find documentation about Drools (5.1+) and JMX. Any articles / documentation available ? 2010/8/3 Quinn, Dan <dequinn(a)fedex.com&gt; Drools(5.1+) has already added functionality to monitor rule activity in > your application using JMX. You can turn mbean rule monitoring on either in > the rulebase’s configuration file(drools.mbeans=enabled||disabled) or you > can configure it through the command line(-Ddrools.mbeans=enabled||disabled > I believe). > > > > *From:* rules-users-bounces(a)lists.jboss.org [mailto: > rules-users-bounces(a)lists.jboss.org] *On Behalf Of *Dieter D'haeyere > *Sent:* Tuesday, August 03, 2010 9:49 AM > > *To:* Rules Users List > *Subject:* Re: [rules-users] Drools Expert: monitor rules & report > activity > > > > What I mean with 'all possible cases' is eg. that you will pass your facts > to the rule engine and that the rule engine will 'return' some result. > I guess it is perfectly possible that in your test scenario's you covered > a lot of possible values for those facts but not all of them and that you > could get some unexpected results afterwards. > This would mean that your test scenario's / test data were not good > enough. But I could imagine that stuff like this happens... At that moment > you should be able to see what rules were fired in a production environment. > > Ik will have a look at the drools execution server. > > Dieter. > > > > 2010/8/3 Swindells, Thomas <TSwindells(a)nds.com&gt; > > Guvnor is a user interface used to define sets of rules, it’s not designed > to be an actual execution server – the demo test scenarios only work on > static predefined data, in a real execution environment the input data has > to be acquired/loaded from somewhere dynamically, hence you always need some > form of development – though look at the drools execution server to minimize > this. > > > > What do you actually mean by covering all possible cases anyway? Possible > cases of what? What are you trying to detect? > > > > Thomas > > > > *From:* rules-users-bounces(a)lists.jboss.org [mailto: > rules-users-bounces(a)lists.jboss.org] *On Behalf Of *Dieter D'haeyere > *Sent:* 03 August 2010 14:35 > *To:* Rules Users List > *Subject:* Re: [rules-users] Drools Expert: monitor rules & report > activity > > > > Ok, this looks like a way to handle it. > But does this mean that there is no 'out of the box' monitoring > possibility ? > > When deploying a rule base (with Guvnor), I would kind of expect that > Guvnor is accessible and that it can return some metrics (eg. after > switching on a monitoring option because I presume continuous logging would > slow down the system too much). > > As I understand it now, some custom development is needed will be needed > to achieve 'real-time' monitoring. > > > > > > > > 2010/8/3 David Sinclair <dsinclair(a)chariotsolutions.com&gt; > > Have a look at the AgendaEventListener. You can use these callbacks to see > which rules fire and information about them > > void > > *activationCancelled<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/AgendaEventListener.html#activationCancelled%28org.drools.event.rule.ActivationCancelledEvent%29> > *(ActivationCancelledEvent<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/ActivationCancelledEvent.html> > event) > > > void > > *activationCreated<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/AgendaEventListener.html#activationCreated%28org.drools.event.rule.ActivationCreatedEvent%29> > *(ActivationCreatedEvent<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/ActivationCreatedEvent.html> > event) > > > void > > *afterActivationFired<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/AgendaEventListener.html#afterActivationFired%28org.drools.event.rule.AfterActivationFiredEvent%29> > *(AfterActivationFiredEvent<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/AfterActivationFiredEvent.html> > event) > > > void > > *agendaGroupPopped<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/AgendaEventListener.html#agendaGroupPopped%28org.drools.event.rule.AgendaGroupPoppedEvent%29> > *(AgendaGroupPoppedEvent<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/AgendaGroupPoppedEvent.html> > event) > > > void > > *agendaGroupPushed<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/AgendaEventListener.html#agendaGroupPushed%28org.drools.event.rule.AgendaGroupPushedEvent%29> > *(AgendaGroupPushedEvent<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/AgendaGroupPushedEvent.html> > event) > > > void > > *beforeActivationFired<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/AgendaEventListener.html#beforeActivationFired%28org.drools.event.rule.BeforeActivationFiredEvent%29> > *(BeforeActivationFiredEvent<http://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/stable/drools-api/org/drools/event/rule/BeforeActivationFiredEvent.html> > event) > > > > 2010/8/3 Dieter D'haeyere <dieter.dhaeyere(a)gmail.com&gt; > > @ll, > I have a question regarding the possibilities to monitor and report on the > rules activity. > I have seen that with Drools Guvnor, it is perfectly possible to monitor > scenario's, see what rules fired, etc. > > Now, going further, I have two questions: > - Is it possible to monitor rule activity (which rules got fired etc) in a > production situation. Eg. Is it possible to start recording activity at > some time until a proble occured and to review the logs afterwards. This > would be of use when scenario's are not covering all possible cases. > - Is it possible to produce reports on rules, usage of rules (eg. what > rules are fired and what rules were fired most), performance, ... > And if not, what could be a good starting point to create them ? > > My experience with Drools is rather limited. Let's say that I am > interested in expert system and technologies surrounding it. At this moment > I am getting a 'theoretical' grip on Drools and its possibilities (of > course, I couldn't help also creating some kind of poc :) ). > > Sincerely, > Dieter D'haeyere. > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > > > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > > > > > ------------------------------ > > > > ************************************************************************************** > This message is confidential and intended only for the addressee. If you > have received this message in error, please immediately notify the > postmaster(a)nds.com and delete it from your system as well as any copies. > The content of e-mails as well as traffic data may be monitored by NDS for > employment and security purposes. To protect the environment please do not > print this e-mail unless necessary. > > NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 > 4EX, United Kingdom. A company registered in England and Wales. Registered > no. 3080780. VAT no. GB 603 8808 40-00 > > ************************************************************************************** > > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > > > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > >