> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/monitoring/sealights-cockpit/execution-monitor.md).

# Execution Monitor

Execution Monitor shows open and completed test executions across all labs. Use it to confirm execution status and identify the associated apps and agents.

To access Execution Monitor, select **Cockpit** → **Execution Monitor**.

{% hint style="info" %}
The Execution Monitor is accessible to Admin and DevOps users only, as per roles and permissions: [User Management - Roles & Permissions](https://docs.sealights.io/knowledgebase/settings/user-management/roles-and-permissions)
{% endhint %}

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

### Find an execution

The page shows executions that started within the selected time range. It sorts them by start time, with the most recent first.

{% columns %}
{% column %} <i class="fa-calendar">:calendar:</i> **Time range**\
Set the period used to find execution starts.
{% endcolumn %}

{% column %} <i class="fa-filter">:filter:</i> **Filters**\
Narrow results by lab, test stage, source, or status.
{% endcolumn %}
{% endcolumns %}

<table><thead><tr><th width="144" valign="top">Column</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">Execution ID</td><td valign="top">Unique identifier for the execution</td></tr><tr><td valign="top">Lab ID</td><td valign="top">The lab in which the execution ran</td></tr><tr><td valign="top">Test Stage</td><td valign="top">The test stage name associated with the execution</td></tr><tr><td valign="top">Start Time</td><td valign="top">When the execution started, shown in your local browser timezone</td></tr><tr><td valign="top">End Time</td><td valign="top">When the execution ended, shown in your local browser timezone; shown as "-" for open executions</td></tr><tr><td valign="top">Source</td><td valign="top">What initiated the execution: Agent, API, or Extension</td></tr><tr><td valign="top">Status</td><td valign="top">Open or Ended</td></tr></tbody></table>

{% hint style="info" %} <i class="fa-clock">:clock:</i> **Open**\
The execution is still running.
{% endhint %}

{% hint style="success" %} <i class="fa-circle-check">:circle-check:</i> **Ended**\
The execution has completed.
{% endhint %}

### Set the time range

Use the time range selector at the top of the page to control which executions are displayed. The selector shows the active range and corresponding date span in your local browser timezone.

Available presets:

* Past 15 minutes
* Past 1 hour
* Past 4 hours
* Past 1 day
* **Last 7 days (default)**
* Last 14 days
* Last 30 days
* Last 60 days
* Last 90 days
* Select from calendar

{% hint style="warning" %}
The time range applies to an execution's **start time**.
{% endhint %}

### Narrow the list

Use the **Search by test stage** field to find executions by test stage name.

Click **Filter** to open the Filters panel. It provides these categories:

* **Lab ID** — select one or more labs from the list. Supports list search and `Equals` or `Contains` matching.
* **Test Stage** — select one or more test stages.
* **Source** — filter by the initiator: `Agent`, `API`, or `Extension`.
* **Status** — filter by `Open` or `Ended`.

Select values across one or more categories and click **Apply**. Use **Clear all** to reset all active filters.

### Open execution apps

Click any row in the execution list to open the Execution Apps panel for that execution. The panel shows all apps that were live in the execution lab, with the following details per app:

* **App Name**
* **Branch Name**
* **Build Name** — hover over the build name to reveal an **Open in Build Monitor** link. This opens the app's Build Monitor entry.

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

### End an execution

Each row in the execution list provides this action at the far right:

* **Force end execution** (stop icon) — ends an open execution immediately. SeaLights keeps coverage already received. You must confirm this action. This action requires the Admin or DevOps role.

<figure><img src="/files/6w8Q7g4lw7PwhoWv3TjQ" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Forcing an execution to end cannot be undone.
{% endhint %}

### Open agent configuration

Each row in the execution list provides this action at the far right:

* **Agent configuration** (`{}` icon) — opens the testing agent’s full JSON configuration. The panel supports expanding fields, copying, and downloading. It is available only for agent-initiated executions.

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


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/monitoring/sealights-cockpit/execution-monitor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.