# Capture console logs

{% hint style="info" %}
available for incoming recordings 
{% endhint %}

In case of complex troubleshooting (eg. you can't replicate the issue on your own environment), console logs are very handy. 

Birdie prevents your team from having to ask customers to open their console logs.

<figure><img src="https://3843507234-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FECPgvsGwy5oMz4WIZw3a%2Fuploads%2FyBSOGRWUvIxVSZYyKuWR%2FConsole%20logs.png?alt=media&#x26;token=9510c085-e786-4896-88fd-1055f3b1e8f0" alt=""><figcaption><p>Capture console logs via Birdie</p></figcaption></figure>

## Install Birdie Snippet

{% hint style="info" %}
Birdie snippet is required to capture console logs.
{% endhint %}

{% content-ref url="../getting-started/snippet" %}
[snippet](https://docs.birdie.so/birdie-docs/~/changes/0VcwZq2bE3lijHZqXNlN/getting-started/snippet)
{% endcontent-ref %}

### Others

<details>

<summary>What if my user has more than 1 window open?</summary>

If more than one browser tab is open with your web app, we will always display the console logs coming from the latest active tab (or window). If the user switches tabs during a recording, the console will also switch to the new focused tab, and it will be notified in the console flow with a "Tab switch" event.

</details>