# Logs

The `retrodeep logs` command enables you to easily access and monitor the logs of your deployments directly from the command line. This feature is crucial for debugging and understanding the behavior of your applications in real-time.

## Usage

View Logs for a Deployment:

```bash
retrodeep logs [deployment URL | deployment ID]
```

Specify either the deployment URL or the unique deployment ID to view logs associated with that deployment.

{% hint style="info" %}
Using `retrodeep logs` with a production url would display logs for the most recent deployment.
{% endhint %}

### Extended Usage

This command supports viewing logs for both current and past deployments, helping you troubleshoot issues or monitor ongoing operations.

#### Examples

**View Logs Using Deployment URL:**

To see the logs for a specific deployment using its URL:

```bash
retrodeep logs example_deployment_url
```

**View Logs Using Deployment ID:**

If you know the deployment ID, you can directly use it:

```bash
retrodeep logs deploymentID
```

{% hint style="info" %}
For comprehensive troubleshooting and audit purposes, reviewing logs frequently can provide insights into the health and performance of your applications.
{% endhint %}


---

# 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.retrodeep.com/retrodeep-cli/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.