# Execution Logs

The **Runbook Execution Logs** page helps you keep track of all your runbook executions across your resources. Whether you’re checking for failures, verifying completions, or reviewing inputs and outputs, everything you need is in one place.

## View Execution Logs

To access all your runbook execution history:

1. **Log in to the OneLens UI.**
2. Navigate to the **Runbook** section from the sidebar.
3. Click on the **Execution** tab at the top of the page.

From this view, you get a complete list of all your runbook executions in a table that’s easy to scan

<figure><img src="/files/2MBkIXOGLQvlYYqbCCZR" alt=""><figcaption></figcaption></figure>

### Search

Use the search bar to quickly find a specific runbook, ticket ID, resource, or account. It helps you get straight to what matters.

### Filters

Refine your view using execution status:

* **Success** – Completed without issues
* **Failed** – Encountered an error
* **Pending** – Yet to finish running

### Key Metrics

At the top of the page, you’ll see a quick summary of your executions:

* **Total Resources Run On** – How many resources were involved
* **Total Successful** – How many runs completed successfully
* **Total Failed** – How many runs didn’t go through

### Table View

Each row in the table gives you detailed info on individual runbook executions:

| Column     | Description                                              |
| ---------- | -------------------------------------------------------- |
| Runbook    | The name of the runbook you executed                     |
| Resource   | The resource where the runbook was applied               |
| Status     | The result of the execution: Success, Failed, or Pending |
| Ticket ID  | The ID of the ticket the runbook was executed on         |
| Run On     | When the runbook was triggered                           |
| Service    | The cloud service involved in the execution              |
| Created By | The user who initiated the run                           |
| Account    | The account where the resource is hosted                 |
| Region     | The region where the runbook was executed                |

## View Logs for a Specific Runbook

To dig into the details of a particular execution:

1. Locate the runbook in the table.
2. Click the **three vertical dots** on the right of the row.
3. Select **View**.

<figure><img src="/files/kQRif2mPHjnOofb1iVV0" alt="" width="375"><figcaption></figcaption></figure>

### What You’ll See

In the detailed view, you'll get full visibility into the execution:

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

| Number Reference | Field               | Description                                                                                  |
| ---------------- | ------------------- | -------------------------------------------------------------------------------------------- |
| 1                | Status              | Whether the execution succeeded, pending or failed                                           |
| 2                | Resource Name       | The specific resource the runbook targeted                                                   |
| 3                | Service             | The cloud service involved                                                                   |
| 4                | Account             | The account where the runbook is executed                                                    |
| 5                | Region              | The region where the runbook was executed                                                    |
| 6                | Ticket ID           | The ticket whose recommendation triggered the runbook                                        |
| 7                | Execution Time      | Time taken to complete the execution                                                         |
| 8                | Input (in JSON)     | The values passed into the runbook at execution time                                         |
| 9                | Output (in JSON)    | The output returned from the runbook execution                                               |
| 10               | Download JSON Files | Dedicated **Download** buttons are available to export both the input and output JSON files. |


---

# 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.onelens.cloud/automate/remediations/runbooks/execution-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.