> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/archive/features-legacy-databutton-web-app-builder/observability-and-debugging.md).

# Observability and Debugging

See what’s happening inside your app, spot issues fast, and decide what to do next. **Observability** in Riff centres on **Logs** - a live stream of messages from your frontend and backend while you build and run the app.

***

### Where to find Logs

* The **Logs** button lives on the **top bar above the Preview**.

Inside the panel you’ll see time-stamped entries from the frontend and backend, including errors, warnings, and any messages you print in code (e.g., `console.log`, `print`).

***

### What the Logs panel can do

* **Send logs to the agent** :wrench: – shares the current log context; the agent can summarize, diagnose, and propose fixes.
* **Clear logs** :broom: – wipes the visible log stream so you can reproduce an issue with a clean slate.
* **Agent reads logs** – the agent may read logs automatically during a task, and you can also explicitly ask it to review them.

> Tip: When you’re about to reproduce a bug, click **Clear logs** first. Then perform the steps to trigger the problem—your capture will be focused and easier to interpret.

***

### Quick workflow: “Something’s wrong”

1. **Open Logs** above the Preview.
2. **Reproduce** the problem once with a clean log.
3. **Send logs to the agent** by clicking on the :wrench:icon, the agent will then automatically work on resolving the issue.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.riff.ai/archive/features-legacy-databutton-web-app-builder/observability-and-debugging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.