---
title: 'Logs'
description: 'Distinguish API, webhook, and LLM logs when diagnosing a request.'
---

# Logs

Open the project’s **Logs** page. The record-type selector provides **API requests**, **Webhook executions**, and **LLM requests**. Select the type before interpreting the list.



## Find a request

Start with the approximate time and operation. The list includes Time, Operation, Status, Duration, Bandwidth, and Location. Open the available details to correlate a failure with the operation that produced it.

| Question                               | Surface                           |
| -------------------------------------- | --------------------------------- |
| Why did a data API call fail?          | API requests                      |
| Was an outgoing webhook delivered?     | Webhook executions                |
| What happened to a model request?      | LLM requests                      |
| Did an automation accomplish its task? | Studio Run History and run detail |
| Who changed a setting?                 | Dashboard Activity                |

A successful HTTP or execution status does not establish business correctness. Check the response or run summary as well. Preserve request identifiers and timestamps for support, while redacting authorization headers, secrets, and customer data.

If you cannot find the event, check project selection, time filters, and record type. See [troubleshooting](/docs/troubleshooting) for the next diagnostic step.


---

[View full sitemap](/docs/sitemap.md)
