The article is related to the statistics of all the rules that gets executed by the application. I am actually looking for only the rules that gets deployed as part of that release (jar file deployment) not the rules that were already existing before the deployment. We would want to make sure that those rules got executed at least once.
Yes, I am actually looking for statistics of only those rules that gets deployed as part of that release (jar file deployment), not the rules that were already existing before the deployment of the jar.
Perhaps someone has a more straight forward answer, but I would suggest proceeding like this:
1) Trace the import mechanism so you can understand what rules are used (probably functions and activities) for opening the zip file and determining exactly the pzinskeys being imported. Use those same rules yourself for storing away a list of the pzinskeys you are interested in monitoring.
2) use a db query to show how many rows exist in each table, and use that query three times, once before the import, once after the import, and once after using your rules. By comparing the first two usages of the query, the tables whose rows have changed show you which tables the imported rules are cached into. By comparing second and third usages of the query, you'll know which db tables the rules are cached into when the rules are actually used. It's this last set of tables you'll be most interested in when you want to know how many of your rules have been used at least once. [ NOTE: Beware that different kinds of rules are cached to different tables. But your usage of the query will help determine the differences ]