Docs

Environment Detail

What this screen is for

Opening one environment takes you to its detail page — the richest screen in Fenwave. It is where you find out what an application is actually doing: its logs, events, metrics, pipeline steps, Kubernetes resources, test results and security findings, plus the actions you can run against it.

Before you start

Everything here is gated by the tier the environment belongs to, following env-by-branch.<env>.<resource>.<action>:

Tab group Typical permission
Observe env-by-branch.<env>.event.read, .pod.read, .deployment.read
Operate .configmap.write, .deployment.restart, .resource.delete
Test the tier’s read permissions

A tab you cannot read is not shown. Seeing fewer tabs than a colleague is a permission difference, not a broken page.

Opening it

From Dev, Staging or Production, click an environment.

  • /ebb/environement/:appName
  • /ebb/cluster/:clusterName/environement/:appName — the cluster-scoped form
  • /ebb/environement/:appName/resource/:resourceName/details — one resource

The interface

📸 Screenshot Placeholder: An environment detail page on the Overview tab. Mark: (1) the header with the environment name, (2) the TTL control, (3) the lock control, (4) the four tab groups, (5) the environment actions on the right of the tab bar.

The tabs are organised into four groups:

Group Tabs What it is for
Observe Overview · Deployment Info · Application Logs · Jobs Logs · Events · Metrics · CronJobs · Activity Logs Finding out what is happening. Start here
Build Pipeline Steps What the pipeline did, step by step
Operate Configuration · Resources · Edit ArgoCD · Actions Changing something
Test Security · Testing · Performance · Quality Results from the test and scan tooling

Two controls sit in the header rather than in a tab:

Control What it does
TTL management Extends or shortens the lifetime of an ephemeral environment
Lock Locks the environment with a stated reason, so it is not changed under someone

Which Observe tab to use

Question Tab
What version is running, and is it healthy? Overview
What did the platform just do? Events
What is the application saying? Application Logs
What did a scheduled job do? Jobs Logs, CronJobs
Is it under load or out of resources? Metrics
Who changed what, and when? Activity Logs

Reaching for Application Logs first is the common instinct and usually the wrong one. Events tells you whether the platform succeeded before you spend time reading the application’s output.

Walkthroughs

Lock an environment

  1. Open the environment.
  2. Use the lock control in the header and give a reason. The reason is the entire point — a lock with no explanation gets removed by whoever it blocks.
  3. Unlock it when you are done.

Extend a dev environment’s TTL

  1. Open the environment and use TTL management.
  2. Extend it.

The dialog offers an Advanced Settings link, which opens the environment configuration page at /ebb/environement/configuration.

Inspect one Kubernetes resource

  1. Go to Operate › Resources.
  2. Select the resource. The detail drawer shows its state.
  3. For a fuller view, or to act on it, use Cluster Console.

Run an action

  1. Go to Operate › Actions.
  2. Choose the action and run it. The run streams its output, and past runs are kept in the run history.

Scenario

An application deployed successfully but returns 502.

  1. Open the environment. Stay on Overview long enough to confirm the version is the one you expect — if it is not, this is a deployment problem, not an application one.
  2. Observe › Events. Look for pods failing to start, image pull failures, or probe failures. If the platform is unhappy, stop here and fix that.
  3. If events are clean, the platform did its job and the application is at fault. Go to Observe › Application Logs.
  4. Observe › Metrics — a 502 that coincides with memory limits is an OOM kill, and no amount of log reading will make that obvious.
  5. Operate › Resources — check the service and its endpoints. A 502 with healthy pods and no endpoints is a selector mismatch, which is a configuration problem rather than a code one.
  6. If you need to change something, Operate › Configuration for config, or Operate › Actions for a defined operation. Prefer either over acting directly on the cluster, because both are recorded in Activity Logs.

The order matters: platform first, then application, then configuration. Going in the other direction is how an afternoon disappears.

When it doesn’t work

Symptom Cause How to check Fix
Fewer tabs than a colleague sees Tabs are gated by the tier’s permissions Access Explorer Ask for the specific permission on that tier
Cannot change configuration Missing env-by-branch.<env>.configmap.write Access Explorer Ask for it on that tier
Environment disappeared while you were working TTL expired (dev only) TTL before expiry Extend the TTL, or lock the environment
An action fails immediately The action’s own preconditions are unmet The run output in the stream panel Read the stream; it names the cause
Metrics tab is empty Monitoring is not enabled for this install — Monitoring is a platform-level setting

Next