# Logging

Integration Gateway integrations generate logs during their execution that can be reviewed for troubleshooting purposes when needed. These logs can be found on the left-hand sidebar under the *Logs* tab for [superuser accounts](/integration-gateway-platform-reference/permissions.md#user-type).

### Types of Logs

Logs are stored at two levels:

* INFO
* DEBUG

INFO logs are always generated when an integration runs and contains basic start, end, and success/failure information.

DEBUG logs provide a further level of detail, including raw request objects. Because DEBUG log entires may contain sensitive information, they must be proactively enabled before the logs are recorded.

### Enabling DEBUG Logging

DEBUG logging is enabled using the toolbar at the bottom of the *Log* page. It can be enabled for 24 hours or 7 days at a time, and will automatically turn off at the end of that period. If DEBUG logging needs to be enabled for longer, an active DEBUG log session can be extended by clicking the *Change Debug Logging Status* button during an active session and choosing the desired duration.

When DEBUG logging is enabled, the DEBUG log entries are visible to all users who have access to the *Log* page.

<figure><img src="/files/fA8n6DvO5kdxCjYsouGb" alt=""><figcaption><p>The <em>Log</em> page toolbar</p></figcaption></figure>

### Viewing Logs

The *Log* page includes a *Log Level Filter* that controls which log entires are displayed:

* INFO level shows only INFO level log entries
* DEBUG level shows both INFO and DEBUG level log entries


---

# Agent Instructions: 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://glyue.docs.sandboxbanking.com/integration-gateway-platform-reference/logging.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.