Metrics

Every Web Application and Background Worker shows live resource usage in the dashboard, so you can see what your app is actually consuming without leaving the page you deploy from.

What is measured

• CPU — processor usage in cores, summed across all of the app’s running instances.
• Memory — working-set memory in bytes, summed across all running instances.
• Throughput (Web Applications only) — HTTP requests per second arriving at the app’s public endpoint.
• p95 latency (Web Applications only) — the response time that 95% of requests beat, in milliseconds.

Throughput and latency are measured at the platform’s edge, so they reflect real traffic to your app’s URL. They only appear for Web Applications, and only once the app has received some traffic — a Background Worker has no public endpoint, so it shows CPU and memory alone.

Where to find them

1. In the dashboard, open your Organization, then the Project and Environment (for example acme → shop → production).
2. Click the app — say web.
3. You land on the Overview tab. The usage panel sits inside the Deployment Status card at the top of the page.

Each metric shows its latest value with a small trend sparkline next to it. If the app has CPU or memory limits configured, the panel also shows usage against the limit — for example 128Mi / 256Mi · 50% — with a bar that changes color as you approach the limit. That makes it easy to spot an app that needs a bigger memory allowance or more instances before it becomes a problem.

For a longer view, open the app’s Usage tab: Live metrics shows the same meters over the last 1 hour, 6 hours or 24 hours (pick the range at the top of the card), next to the app’s bandwidth this month.

Time range and freshness

The Overview panel shows the last hour of data at roughly one-minute resolution (the Usage tab’s 6-hour and 24-hour ranges use 5- and 15-minute steps). While the page is open it refreshes automatically every 30 seconds, so you can watch the effect of a deployment, a scale change, or a traffic spike as it happens.

When metrics are missing

• “Resource metrics unavailable” — the installation you are using has no metrics backend configured. Ask your platform operator.
• “No recent samples” — the panel is working but has nothing to show yet. A freshly deployed app takes a short while to produce its first samples, and a stopped app (zero instances) produces none.
• No throughput or latency meters — either the resource is a Background Worker, or the Web Application has not yet received any HTTP traffic.

A metric that temporarily fails to load shows as an empty series rather than an error; the rest of the panel keeps working.

Metrics and the CLI

There is no paas command for usage metrics today — they live in the dashboard. From the CLI you can still check on a running app:

paas status -o acme -p shop -e production -a web # deployment status and health
paas ps -o acme -p shop -e production -a web   # list the app's running instances
paas logs -o acme -p shop -e production -a web --tail

Using metrics to act

• Memory climbing toward its limit on every instance: raise the app’s memory limit or add instances — see Scaling & Autoscaling.
• CPU pinned high while p95 latency grows: add instances, or turn on autoscaling so the platform does it for you.
• Throughput at zero when you expect traffic: check Logs and the app’s public URL on its Overview tab.

Next steps

• Scaling & Autoscaling — act on what the meters show
• Logs — pair usage numbers with what the app is printing
• Deployments, Health Checks & Rollback — correlate a change in the graphs with a deployment
• Plans, Limits & Usage — how per-app limits are set