Execution trace for decision runtime

An execution trace shows an actual graph or tree of information that represents the execution of a decision service. You can display an execution trace by specifying the executionTraceFilters parameter in the request body when your application calls a decision service with the decision runtime REST API.

The executionTraceFilters parameter is a JSON object that specifies which traces are activated in which format.

If this parameter is not set, the execution trace is null as a result.

The format for the request body in JSON payload:

{
  "executionId": "<value_1>",
  "input": "<value_2>",
  "executionTraceFilters": { ... }
}

Tip: You can use the objectsInMemoryLimit option in TraceConfiguration to manage the memory used by the trace.

For more information about the parameters, see the schema of TraceConfiguration in the decision runtime REST API reference in Reference.

Sample

The sample Exploring the execution trace is available in GitHub. With this sample, you can build an HTML page and explore execution traces. It also contains a sample request body for displaying execution traces. Click Decision Intelligence Client Managed Software samples External link opens a new window or tab to be redirected to the GitHub repository.