Environments on ZopDay: CPU, Deploys and Activity on One Canvas
Open Overview in the canvas bar to see how a whole environment is doing. The panel has three tabs: Overview, Deployments and Activity. Overview shows CPU, memory and pods. Deployments shows every service with its share of CPU and memory. Activity shows every deploy with who shipped it, how long it took and what changed.
Overview Shows CPU, Memory, Pods and the Top CPU Users
The Overview tab shows CPU, memory and pods for the environment. Services that are deploying or failed appear in the same view. The top CPU users are listed alongside the resource numbers.
| What the Overview tab shows | Detail |
|---|---|
| CPU | Current CPU usage for the environment |
| Memory | Current memory usage for the environment |
| Pods | Pod count for the environment |
| Services deploying or failed | Services that are not in a steady state |
| Top CPU users | Services that consume the most CPU |
CPU, memory, pods, deploying or failed services, and the top CPU users are all on one screen in the Overview tab.
Teams that manage developer seats at the organisation level can open the Overview tab to check the environment before a deploy.
Deployments Lists Every Service With Its Resource Share
The Deployments tab shows every service in the environment with its share of CPU and memory. A filter and search are available to narrow the list.
Every service appears in the list with its CPU share and memory share. The filter and search narrow the list to the services the team needs.
Teams using role-based access controls to govern their organisation can use the Deployments tab to review resource share across services.
Activity Shows Every Deploy With Who Shipped It, Duration and Changes
The Activity tab shows every deploy, newest first. Each entry includes who shipped it, how long it took and what changed. Values that look like secrets are masked.
| What the Activity tab shows | Detail |
|---|---|
| Every deploy | Listed newest first |
| Who shipped it | The person who triggered the deploy |
| How long it took | Duration of the deploy |
| What changed | The changes included in the deploy |
| Secret values | Masked so they do not appear in the log |
The newest deploy appears at the top of the list. Each entry carries the name of who shipped it, the duration and a summary of what changed. Any value that looks like a secret is masked in the activity log.
Teams that track service-level status can use the Activity tab to see the deploy history for the environment.
