> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/intelligence/intelligence-introduction.md).

# Intelligence Introduction

The Intelligence section helps you monitor, inspect, and analyze rule executions using audit logs. It gives you access to both individual execution records and aggregated statistics, so you can understand how your rules are used, what results they produce, and where potential issues may occur.

{% embed url="<https://www.youtube.com/watch?v=kz-v9dkFJlg>" %}

## Enable or disable audit logging

Audit log creation can be enabled or disabled in **Rule Settings**, which are available from the left menu in the Designer tab of each rule.

<figure><img src="https://437457296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MN4F4-qybg8XDATvios%2Fuploads%2Fb4S29y700vwEq3J5zu1p%2FScreenshot%202026-07-09%20at%2013.02.59.png?alt=media&amp;token=e2910966-23f8-4442-beeb-c73d5bdffe55" alt=""><figcaption></figcaption></figure>

When Audit Logging is turned on, executions of the rule are stored as audit logs and can be reviewed later in the Intelligence section. When it is turned off, new executions of the rule are not saved as audit logs.

You can also configure related audit log settings here:

* Debug Data&#x20;
* Propagate Audit to children
* Audit Lifespan

{% hint style="info" %}

### **Propagate Audit to children**

This option allows audit logging to be applied automatically to rules that are executed as part of a rule chain.

This means you do not need to enable audit logging separately for every rule that may be called by another rule, such as a rule executed from a Business Rule node in a Decision Flow or a rule solved from code in a Scripting Rule.

If audit logging is enabled both through propagation and directly on an individual child rule, the execution may be logged twice: once from the parent rule propagation and once from the child rule’s own audit logging settings.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.decisionrules.io/doc/intelligence/intelligence-introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.