Trace data can be retrieved from any long-running server. It creates a step-by-step trace of how your rule set is being processed by the X Engine. This is particularly useful for finding problems in web application rule sets.

To start a trace, simply click the Start trace button on the server status page as shown below.

Once the trace is in progress, you will see the status screen change as shown.

The trace mode will be active for a maximum of 20 transactions, after which it will automatically turn off.

To retrieve and view the trace data, simply click the Get trace data button and supply a repository and file name.

Once the trace data has been retrieved, you can view it by selecting it in the administration tree.

The view of the trace can also be downloaded or deleted (as shown below).

The trace has a number of simple text entries. The following tags are samples of the informational messages and help determine the flow:

Tells you that a new transaction was started and the time it happened.

Tells you that the variable MAXPAY was set to 25.

Tells you that a variable named ERROR was deleted.

Tells you that the rule set entered a given rule.

Tells you which chain point was used from a given rule.

Tells you that the rule set returned from a nominated chain point.

Tells you that the Set Completed rule was called and the scope set.