Skip to content

Add a by-deployment tab on the project metrics page - #342

Open
acoshift wants to merge 1 commit into
mainfrom
project-metrics-by-deployment
Open

acoshift wants to merge 1 commit into
mainfrom
project-metrics-by-deployment

Conversation

@acoshift

@acoshift acoshift commented Oct 9, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Add a By deployment tab on the project metrics page.
  • The tab calls project.metricsByDeployment and charts CPU, memory, pod egress, requests, and static storage, one series per current deployment.
  • Disk, replicas, and cache egress stay on the Project tab. Those are not stored per deployment.
  • A 90d range left in the URL by the Project tab is not rewritten. This tab requests 30 days until the range control is changed. The samples are kept for 30 days.

Numbers will not match the Project tab. That tab reads the daily project rollup (including cache and WAF egress). This tab reads the per-deployment samples.

Contract: deploys-app/api#141. Handler: deploys-app/apiserver#265. Docs: deploys-app/docs#77.

Screenshots

Project By deployment
project by deployment

Mobile:

by deployment, mobile


Requested via Grok Work
Prompter: ACS

Groups the samples already stored per deployment into one chart series
each. Disk, replicas, and cache egress stay on the project tab.

Prompter: ACS
@deploys-app

deploys-app Bot commented Oct 9, 2026

Copy link
Copy Markdown

Preview console-pr-342

URL: https://console-pr-342-606515731026706458.rcf2.deploys.app

Image: registry.deploys.app/deploys-app/console@sha256:5e769cab7c2183f27690963fe284e11b5730a5e59bb7be0fa2bb28914d0e4bbe

Commit: f218df9

updated 2026-10-09T08:52:04Z

This branch was successfully deployed

1 active deployment
pr-342 — f218df9b Deployed Oct 9, 2026 by deploys-app[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant