App overview

What this feature is for

App overview is the workspace landing point for a specific application. It brings recent checks, release context, health signals, and unresolved work into a single operator view. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.

Before you open it

A project with a production URL and at least one meaningful customer path.

Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.

Run the workflow

Use the overview before a release review or incident handoff. Confirm the app identity, scan the highest-impact card, and open the linked evidence rather than treating the summary score as the diagnosis.

1. Open the feature from the dashboard outcome hub.
2. Choose the app and environment that match the decision you are making.
3. Run or save the configuration, then wait for the evidence state to settle.
4. Assign the next action to an owner before leaving the page.

Read the evidence

The overview connects status to the originating check, incident, deploy, or provider row so the next action is traceable. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.

When the result is not healthy

If the view is empty, create an app or connect a provider first. If the view is noisy, reduce the number of low-value checks before changing alert thresholds.

Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.

Use it with the rest of PreFlight

Start in Audit for a complete baseline, then use Deploy or Health depending on whether the decision is about a change or a live system. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.