> For the complete documentation index, see [llms.txt](https://docs.ingestlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ingestlabs.com/tag-manager/live-debugging/view-requests-from-a-live-debugging-session.md).

# View Requests From a Live Debugging Session

## Introduction

Live Debugging is performed either in Staging environment or in the Production environment.

## Procedure

To perform Live Debugging on Ingest Labs:

**Step 1:** Select **Live Debugging** on the left navigation panel.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FMQiIyjf9KfFoRioN3QnJ%2Fimage.png?alt=media&amp;token=44a3424f-c5c0-4866-b565-5ee7f9c0bdf3" alt=""><figcaption></figcaption></figure>

**Step 2:** There are two environments present:

* **Production** – When elements are pushed to the production environment, you can check the live details in the production environment.&#x20;
* **Staging** – When elements are pushed to the staging environment, you can check the live details in the staging environment.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2Faa6Soo5HNkk0PUKSqmjN%2Fimage.png?alt=media&amp;token=69a0b131-5729-4b2f-9e00-25335dfeec19" alt=""><figcaption></figcaption></figure>

For this demonstration we have taken example of Production, click Production.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FCAK4Dn1HMGxrYfDIKqQ1%2Fimage.png?alt=media&amp;token=6f627829-927b-4549-afeb-c64a88849154" alt=""><figcaption></figcaption></figure>

**Step 3:** Click **Start Debugging** on the top right corner of the screen.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2F7qCFNjal0H2ZLElp2SUk%2Fimage.png?alt=media&amp;token=dacd0585-14d0-425b-9acb-3595e36fbd79" alt=""><figcaption></figcaption></figure>

**Step 4:** Enter the Debug ID in the **Debug ID** field or click **Start** to start the debugging session. You need to enter a Debug ID to see events exclusively from your session on the website.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2FZXz8lWgl38hXopjm1tqK%2Fimage.png?alt=media&amp;token=08b129d0-2600-4a54-ae86-593941ad79cb" alt=""><figcaption></figcaption></figure>

The following screen appears:

**Step Result**: The live debugging details appear on the screen. Now, you can view all the events firing in real time, only for your session on the website, for debugging purposes.

<figure><img src="https://2731380315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2F5NgJKJltTKxoNxN36QZP%2Fimage.png?alt=media&amp;token=82c24c91-4820-4859-87a1-00c2fb085520" alt=""><figcaption></figcaption></figure>

**Note 1**: The Debug ID is unique and is meant to streamline traffic tracking. Without a debug ID, you will be bombarded with general traffic data. Using a debug ID will help to streamline data and view the traffic for a particular session. A debug ID is not mandatory for Staging. A Debug ID is required for Production due to the huge network traffic.

**Note 2:** To retrieve the Debug ID, follow the procedure **Retrieve the DebugID Using Console**.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDMDmegqZUJFhJhF4JQG%2Fuploads%2F3IIKCJrXWuyzoMl01Iyy%2FUsing%20Debugging%20Session.mp4?alt=media&token=e0d59b52-2222-4542-9ff8-6ecdd0b8e6dc>" %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.ingestlabs.com/tag-manager/live-debugging/view-requests-from-a-live-debugging-session.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.