# logs

The cldkctl registry logs command displays the logs for a specific registry in the project. This command shows log entries related to the registry’s operations, including events, actions, and other related activities.

## Usage

```
cldkctl registry logs [registry name] [flags]
```

## Aliases

```
logs, log
```

## Steps

Follow the steps below to run and view the result of this command:

1. Make sure to specify the registry name using the --registry global flags before the subcommand.
2. Run the following command in your terminal and replace \<registry\_name> with the name of your target registry.

```
./cldkctl --registry <registry_name> registry logs
```

3. Refer to the Registry List section to view the available registry names.
4. Once executed, the command displays the list of log entries associated with the selected registry.

<figure><img src="/files/agKK6sd0TgC0Y0Pw99As" alt=""><figcaption></figcaption></figure>

| Column        | Description                                    |
| ------------- | ---------------------------------------------- |
| Username      | The user who performed the action.             |
| Resource      | The name of the registry or resource affected. |
| Resource Type | The type of resource being logged.             |
| Operation     | The type of operation performed.               |
| Time Stamp    | The date and time when the action occurred.    |

## Flags

{% hint style="info" %}
This command supports [global flags](/cloudeka-api-list/global-flags.md). Refer to the Global Flags section for details.
{% endhint %}

| Flag                 | Description                                      |
| -------------------- | ------------------------------------------------ |
| -h, --help           | Help for the registry logs command.              |
| -p, --project string | Specifies the project ID to scope the operation. |


---

# 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.cloudeka.ai/cloudeka-api-list/command-reference/cldkctl-registry/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.