The rules section defines the list of monitoring rules to load.
The following loading directives are available:
rule_set : refers a file containing a set of Jeyzer monitoring rules
rule_sets : refers a set of Jeyzer monitoring rules stored in a Jeyzer repository.
Those rules belong usually to a shared profile.
The repo URL format must be used, referencing a set of dependencies defined in the analysis profile.
dynamic_rule_sets : rules get automatically loaded from shared profiles at analysis time.
See the automatic loading section for more details.
all_applicative_rules : indicates if the applicative rules must be enabled to process the applicative events emitted through the Jeyzer Publisher and made available in the JZR recording.
Filter directives are available :
include_ref_patterns: is a list of comma separated applicative event code regular expressions.
This is a white list. If not specified, all applicative rules are considered.exclude_ref_patterns: is a list of comma separated applicative event code regular expressions.
This is a black list, applied after the include if any.
task_applicative_rules, session_applicative_rules, system_applicative_rules : indicate if the applicative rules must be enabled to process respectively only the task, session or system applicative events.
This type of rule loading directive is useful in the JZR report when specializing the event sheets.
The above include and exclude directives can apply as well on those rules.
jeyzer_publisher_rules : indicates if the Jeyzer Publisher rules must be enabled to process the Jeyzer Publisher internal events made available in the JZR recording .
<rules>
<rule_set file="${JEYZER_ANALYZER_CONFIG_DIR}/monitor/rules/standard_rules.xml"/>
<rule_sets files="repo://base/@@base-shared-deps@@"/>
<dynamic_rule_sets declared_repository_only="true"//>
<all_applicative_rules exclude_ref_patterns="DEBUG_EVENT_.*"/>
<jeyzer_publisher_rules/>
</rules>