> 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.md).

# SeaLights Cockpit

Monitor builds, agents, executions, and configuration changes from the Cockpit.

Use the Cockpit to investigate reported builds, active agents, test executions, and configuration changes.

Cockpit has five views. Each card below opens one view.

Select **Cockpit** in the SeaLights navigation menu.

<figure><img src="https://4057366433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjqTCMRYvHhDgsdPLUnc%2Fuploads%2FPhaHEEB9b9zBamal3uCl%2FScreenshot%202025-07-31%20at%2013.07.27.png?alt=media&amp;token=9231c9cb-edf9-44ad-b994-38f7ac155111" alt="SeaLights navigation menu with the Cockpit option highlighted."><figcaption><p>Select <strong>Cockpit</strong> from the SeaLights navigation menu.</p></figcaption></figure>

{% hint style="warning" %}
Cockpit menu is accessible only by ***SeaLights DevOps*** users, as per roles & permissions: <https://docs.sealights.io/knowledgebase/settings/user-management/roles-and-permissions>
{% endhint %}

### Cockpit pages

<table data-view="cards"><thead><tr><th>View</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td><i class="fa-cube">:cube:</i> <strong>Build Monitor</strong><br>Inspect a build, its scans, and test-stage executions.</td><td><a href="/knowledgebase/setup-and-configuration/monitoring/sealights-cockpit/build-monitor.md">Build Monitor</a></td></tr><tr><td><i class="fa-microchip">:microchip:</i> <strong>Live Agents Monitor</strong><br>Find active agents and inspect their configuration.</td><td><a href="/knowledgebase/setup-and-configuration/monitoring/sealights-cockpit/agent-monitor.md">Live Agents Monitor</a></td></tr><tr><td><i class="fa-clock-rotate-left">:clock-rotate-left:</i> <strong>Audit Log</strong><br>Review Dashboard Settings changes.</td><td><a href="/knowledgebase/setup-and-configuration/monitoring/sealights-cockpit/audit-log.md">Audit Log</a></td></tr><tr><td><i class="fa-circle-check">:circle-check:</i> <strong>Dashboard build statuses</strong><br>Understand build-status outcomes.</td><td><a href="/knowledgebase/setup-and-configuration/monitoring/sealights-cockpit/dashboards-build-statuses.md">Dashboard build statuses</a></td></tr><tr><td><i class="fa-list-check">:list-check:</i> <strong>Execution Monitor</strong><br>Track open and completed test executions.</td><td><a href="/knowledgebase/setup-and-configuration/monitoring/sealights-cockpit/execution-monitor.md">Execution Monitor</a></td></tr></tbody></table>


---

# 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.sealights.io/knowledgebase/setup-and-configuration/monitoring/sealights-cockpit.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.