Tracing a rule
Tracing enables you to follow the flow of events through each rule phase. Tracing the execution of a rule also helps Knowledge Base developers to find logical errors or enhance performance. {
The MRL compiler (mccomp) generates rule trace code that contains the following fields:
- Message id (identifying the type of statement being executed)
- Source file name
- Source line number
- Name of the rule
- Reference to the main event being processed
- Class name of the main event being processed
This code is generated each time the compiler is run. Impact on performance is minimal when rule trace is not enabled.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*