Skip to main content
Open an application from Applications and its page replaces the sidebar with the application’s own menu. The menu starts with Overview and a Deploy group that holds Environments, Pipelines and Previews. Then comes one row per view, and last a Technical details group that holds Where it runs. This page lists every row, in menu order, with what it shows. Every view lives at one address, /next/applications/<application-id>?view=<view>, and a view with sections or tabs adds &section=<section>. The Overview has no view. Links saved before the menu changed still open where they meant, except a bare view=settings: it opened Secrets, and it now opens Settings on Address. Most views show one environment at a time: pick it in the environment menu at the top of the page. Logs and Metrics share their time range, and the place picked under Running on stays picked between Logs, Metrics and Architecture.

The menu

Overview

The application’s front page: one card per environment, with what it runs and what it follows (such as Follows pushes to main). Find an environment filters the cards. Add beside the environments starts a new environment on another cluster: see Environments and branch rules. When Ankra has a setup change for the application, the Overview says A setup change is waiting for your approval. When a release did not go live, the environment’s card offers to put the previous version back: see Roll back an application.

Environments

What is live in each environment, and the way to change it. Environments is one page with these parts:
  • What’s live: the version each environment runs.
  • Deploy a version (section=deploy): choose where the application goes and which version. Ankra checks the cluster has what it needs, and nothing changes until you confirm. Until anything of a new application runs, this part shows its Go live steps instead, and opening the application lands here: see Ship your app.
  • Promote a version: with two or more environments, move the build one environment runs onto the next.
  • Recent releases on environment, with Full history linking to History.

Pipelines

Every build of the application, and how its pipeline is set up. Pipelines has four tabs and opens on the first. See Ankra Pipelines.

Previews

A running copy of a branch, to try before it is merged. Each preview has its own address, and Ankra removes it when its timer ends. New preview starts one from a branch that has a published build; each running preview has Open preview and Stop preview. What new previews start from is set in Settings → Deploys, under Preview defaults. See Preview a branch.

History

Every change to the application: what changed, where, who did it and how it ended. A release line you may undo carries Roll back to version or Undo this release: see Roll back an application.

Logs

What the application’s containers wrote, read live or searched over a time range. See Logs.

Metrics

How the application answers requests and what it uses, for the place and the time range you choose. See Cluster metrics.

Security

What the last scans found in the image the application runs and in its code. Filter the findings by severity and open one for what it is and how to fix it; Fix with Ankra (or Ask Ankra how to fix it) hands it to Ankra AI. See Security scanning.

Data

Data has three tabs and opens on the first:

Cost

What the application costs, with Explore application cost for the detail. The row appears only where cost is enabled for the organisation; anywhere else the view reads Cost is not enabled for this organisation. See Cloud Cost.

Secrets

API keys, passwords and connection strings the application reads when it runs, kept per environment, and Shared secret defaults for every environment.

Architecture

What receives requests, what runs and where the application keeps its data, for the place picked under Running on.

Settings

Settings has one tab per section and opens on Address. Each tab says what it is for under its title.
See Environments and branch rules for Deploys, and PR preview environments for Pull requests.

Where it runs

Every place the application runs, by environment, and how each one is doing.