PlatformOperate
Know if an app is down or slow, before users do
See at a glance whether every app is up, how fast it is responding, and how much memory and compute it is using. A degraded app or a slow response shows here before a user notices — no logging into four consoles to find out.
Health by app · live
| App | Status | CPU | Memory | p95 | Errors |
|---|---|---|---|---|---|
| Contract HubLegal | Healthy | 34% | 1.0 / 2 GB | 240ms | 0.1% |
| Vendor RiskLegal | Degraded | 92% | 1.8 / 2 GB | 1.8s | 2.1% |
| HR OnboardingHR | Healthy | 22% | 0.4 / 1 GB | 180ms | 0.0% |
| IT HelpdeskIT | Healthy | 41% | 0.6 / 1 GB | 90ms | 0.3% |
Vendor Risk · p95 response · last 6 hours
Example data shown for illustration.
01The change
One screen instead of four
Before
Four consoles to find out what's wrong
- Uptime in one tool, memory and CPU in another
- A slow app noticed only when someone complains
- No single view of which app is degraded right now
- Digging through logs to find what got slow, and when
With Cenna
Up, slow, or hungry — visible on one screen
- Every app's status, memory, and CPU in one view
- Response time per app, so slowness surfaces first
- A degraded app flagged before a ticket lands
- The moment things got slow, right there in the trend
02What it answers
What it tells you
The operational questions you would otherwise open four consoles to answer.
Is it up?
Every application's status in one place — healthy, degraded, or down — so an outage shows here before anyone reports it.
Is it slow?
Response time per app, with the trend behind it, so a slowdown surfaces while it is still a graph and not a complaint.
Is it running hot?
CPU and memory per app, so one that is close to its limit is visible before it starts dropping requests.
Is it erroring?
Error rate per app, so a spike in failures points you straight at the application throwing them.
03Ask it
Or just ask the fleet
The same signals are answerable in plain language. Ask what is down, what is slow, or what is running hot — and get a specific answer, not a dashboard to go read.
Ask it anything about your fleet
- Is anything down right now?
- Why is Vendor Risk slow?
- Which app is using the most memory?
- Has anything been erroring today?
- Is anything close to its CPU limit?
Status across every app · Memory, CPU, and latency · Answers, not dashboards
Is anything down or degraded right now?
One app degraded — Vendor Risk.
Three of four are healthy. Vendor Risk is degraded: its p95 response climbed from 400ms to 1.8s at 13:00 and CPU is pinned at 92%. It is still serving, but slowly. The other apps are well within range.
04FAQ
Common questions
How fresh is this?
It reflects live status and metrics, syncing continuously rather than on a daily batch, so the health you see is the health right now.
What makes an app show as degraded?
A failing health check, a response time well above its normal range, or resource use near its limit. Any of those flags the app here before it turns into a support ticket.
Where do the metrics come from?
From the app's own runtime in your cloud — CPU, memory, latency, and error rate — read back into the console. Cenna does not add an agent to your workloads to collect them.
Can we get alerted instead of watching?
Yes. The same signals drive alerts, so a degraded app or a latency spike can notify the owning team rather than waiting to be noticed on the screen.
See a degraded app caught before its users do.
Thirty minutes on a live fleet: we find the slow app, trace it to its cause, and show the status, memory, and error signals that surfaced it — the questions you would otherwise open four consoles for.
Get a DemoBuilt for speed. Engineered for control.