> 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/space/audit-logs.md). # Audit Logs The **Audit Logs** page provides a detailed record of all audit logs generated by space rules, allowing users to track and review system activities efficiently. The logs are displayed in a sortable list, which can be organized by rule, creation time, or HTTP status code for easy navigation. The **Audit Logs** section is part of the **Space module** and provides a searchable, filterable table of all rule execution logs within the current space. Audit Logs are designed to help: * Review past rule evaluations * Track input and output data for each evaluation * Filter logs by specific rule, version, correlation ID, or date * Identify patterns, anomalies, or failed evaluations * Export or delete outdated log data
For more details, see the [**Business Intelligence** section](/doc/business-intelligence/audit-logs.md). There, you'll learn how to enable logging for individual rules, how audit logs are counted and billed, and how to manage log storage effectively. ### Business Intelligence API For more advanced insights and data analysis, the **Business Intelligence** section in the documentation provides guidance on generating audit logs and utilizing them for reporting. Additionally, for automated access and integration, the [**Business Intelligence API**](/doc/api/bi-api.md) section explains how to retrieve audit logs programmatically, enabling seamless data access for external monitoring and reporting systems. --- # 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/space/audit-logs.md?ask=&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.