> 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/cli/release/instances/logs.md).

# release instances logs

Command reference doc for the Release CLI

Tail logs from a running instance

## Description

Tail logs from a running instance

If an --environment flag is not provided it can be selected interactively through a fuzzy finder interface.

If the INSTANCE argument is not provided it can be selected interactively through a fuzzy finder interface. If it is provided but matches more than one instance, the matching instances will be shown in the fuzzy finder.

```
release instances logs [INSTANCE] [flags]
```

## Examples

```

Tail instance logs selecting the environment interactively:
> release instances logs

Tail instance logs in a specific app and environment:
> release instances logs --app web --environment staging

Tail instance logs for a specific service instance:
> release instances logs backend
```

## Options

| `--account <string>`     | Account name or ID (default: $RELEASE\_ACCOUNT or "account" in config file)                                                                                                                                                                                                       |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `--app <string>`         | App name or ID (default: $RELEASE\_APP or "app" in config file)                                                                                                                                                                                                                   |
| `--environment <string>` | Environment handle or ID                                                                                                                                                                                                                                                          |
| `--if-multiple <string>` | Behavior when multiple instances match the query. Options: - last: Automatically select the last matching instance - random: Automatically select a random matching instance - prompt: Interactively select an instance - first: Automatically select the first matching instance |

## Options inherited from parent commands

| `--config <string>` | config file (default is $HOME/.release.yaml) |
| ------------------- | -------------------------------------------- |
| `--debug`           | enable debug logging                         |

## Related

* [release instances](/cli/release/instances.md) - Manage instances


---

# 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/cli/release/instances/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.