> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/control-center/observe/db-query-logs.md).
# DB Query Logs
Audit database operations executed by the platform.
DB Query Logs records the database operations the platform executed. Open **Observe → DB Query Logs**.
DB Query Logs, the default view.
Filtering DB Query Logs by module.
You can narrow by project and module. You can also search the log. Filter by these modules:
* **Agent**
* **App**
* **Skill**
* **Integrations**
* **Marketplace**
* **Platform**
Each row is one operation:
| Field | What it shows |
| ------------- | --------------------------------------------------------------------------------------------------------------- |
| **Module** | The area the operation belongs to, such as **Agents**, **Guardrails**, **Knowledge**, **MCP**, or **Accounts**. |
| **Operation** | The operation in `schema.table.action` form, such as `agents.agent.update`. |
| **User** | The actor that triggered it. |
| **Timestamp** | When it ran. |
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul AI-assisted, human-approved
{% endcolumn %}
{% endcolumns %}
---
# 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.uptiq.ai/ai-workbench-qore/control-center/observe/db-query-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.
