> 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/whats-new/october-2026/coverage-analysis-now-supports-integration-builds.md).

# Coverage Analysis Now Supports Integration Builds

Customers who track integration environments with SeaLights integration builds can now use the new Coverage Analysis too. Select an integration build once, and SeaLights shows you coverage for every app inside it.

### What's New

Until now, the new Coverage Analysis worked only with the newer SeaLights onboarding approach. Teams still using integration builds, the earlier way of onboarding to track integration environments, could not benefit from it.

That gap is closed. Coverage Analysis now supports integration builds, so you can:

* Include an integration build in a Coverage Analysis view, just like any other app
* See each app in the integration build as its own line in the Apps view
* Get the same coverage insights as customers on the new onboarding approach, without changing how you onboard

### How It Works

An integration build is a defined set of apps that SeaLights reports on as a single app. When you create a Coverage Analysis view and select an integration build, SeaLights automatically splits it into the apps it contains.

The result is the same as if you had created a view that included all of those apps individually. Even though you selected only one app, the Apps view lists each underlying app on a separate line, so you can see where coverage is strong and where it falls short for each one.

There's nothing extra to configure. Select the integration build when creating your view, and the split happens automatically.

### Get Started

* Create a new Coverage Analysis view and select your integration build as the app


---

# 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/whats-new/october-2026/coverage-analysis-now-supports-integration-builds.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.
