# Debugging with Live Logs

Troubleshooting is key for deployed applications. This tutorial shows how to use Chassy's Live Logs to diagnose and resolve issues by accessing, navigating, and interpreting the interface to find root causes.

## Prerequisites

Before we start this tutorial, you will need:

* An existing [Fleet](/user-guides/fleet-user-guide.md)
* A [connected machine](/user-guides/fleet-user-guide/enrolling-machines.md) with an application deployed

{% hint style="info" %}
To learn how to deploy an application, follow our [Deploy an Artifact](/tutorials/deploy-an-artifact.md)tutorial.
{% endhint %}

## Accessing the machine

Now that everything is set up, we can find the specific machine that is running the application.

1. Go to the *Fleet* section of Chassy Console.
2. Find the Fleet that the machine belongs to.
3. Select the machine by clicking on its green box.

<figure><img src="/files/wzFTyeDiM2ZHh37g2NBl" alt="The Fleet panel of Chassy Console shows the fleets and machines enrolled into your Chassy workspace."><figcaption></figcaption></figure>

You can also click on the Machines tab and search, sort, and filter through all enrolled machines.

<figure><img src="/files/CGUgrkX2TB4ITIm5tHEB" alt="The Machines tab on the Fleet panel has search, sort, and filter options to help you find the device."><figcaption></figcaption></figure>

Once you find the machine, click on it to open up the side panel with details. If it is currently online, you'll find the option to open *Live Logs.*

<figure><img src="/files/0N3dlEZdRkOHvD76Y5Oi" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Can't find the *Live Logs* option? Check that the machine is currently online, and that there is an active deployment
{% endhint %}

## Searching through *Live Logs*

The Live Logs page shows everything that is being printed from the deployed application, split between the channels `stdout` and <kbd>`stderr`</kbd>.

<figure><img src="/files/hg7oOppIPficMHVcqD07" alt="The Live Logs shows in realtime what is printed out from your device&#x27;s application."><figcaption></figcaption></figure>

You can use the search bar to quickly parse through the lines, as well as toggle word-wrap for better readability.

If you have multiple applications running on the machine, use the dropdown to select the application whose logs you want to view.

## Troubleshooting

### Why can't I find the *Live Logs* button?

*Live Logs* will only appear if the machine is online, has an operating system running the Chassy agent, and currently has an active application deployed.

The Chassy agent is only available on Linux, Windows, and NixOS.

### How do I know which machine I deployed to?

To find the machine, go to the *Machine* tab on your *Fleet* panel. You'll be able to see all active deployments on each machine, and can also filter the list by the application deployed.

### Why does it say I'm disconnected?

There is a 10 minute limit imposed to avoid streaming data indefinitely. Simply click on the *Connect* button on the top right, and you'll be able to read all logs.

## Conclusion

In this tutorial, we've walked through the process of accessing and utilizing Chassy's Live Logs feature. You now know how to view `stdout` and `stderr`, filter information, and troubleshoot issues to diagnose and resolve problems in your deployed applications. This tool offers valuable real-time insight, helping you maintain healthy and reliable deployments.


---

# 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://docs.chassy.io/tutorials/debugging-with-live-logs.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.