> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/guides-and-examples/running-instances/viewing-logs.md).

# Viewing logs

How to view logs for a specific instance or container

In any of your environments, you can see a list of instances associated with that environment.

![Opening the Release log viewer](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-da94901df954096a9875bec0f6a9c8e88e71c2bb%2Fview-instance-logs.png?alt=media)

Click on the **Logs** button to the right of a specific instance to get a web-based log viewer showing the latest logs from that instance.

From this log viewer, you can:

* **Download** the logs: This will download a `.txt` version of the logs.
* **Clear** the logs: Clear the current output to see newer entries more easily.
* **Reset** the logs: If you have previously cleared the output, resetting the viewer will bring back the previously cleared output.

![Log viewer controls](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-6336f1b8061c094cb040cf1faa71f8d2d66aab7e%2Fviewing-logs-log-controls.png?alt=media\&token=a358cfa8-4247-48e0-b684-d311e9c0bdc0)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.release.com/guides-and-examples/running-instances/viewing-logs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.