Observability overview

The overview is your app's health dashboard — one screen that tells you whether everything's running fine right now. It shows four vital signs at a glance, so you don't need to dig through anything to know if your app is healthy. If something's wrong, this is where you'll spot it first.

Annotated screenshot of the Observability overview dashboard showing four metric tiles in a row — Health (green), Error rate, Latency, Traffic — callout: "Your app's vital signs at a glance."

What it's for

Think of it like the dashboard in a car. You don't need to understand the engine — you just glance at the dials and know everything's fine, or that something needs attention. The overview gives you that same instant read on your live app.

The four signals

Health

The headline answer: is your app up and working? Green means everything's running normally. If it turns red or amber, something needs your attention — and the other three signals tell you what.

Error rate

How often something is failing. In plain terms, this is how often your app breaks for someone — a request that didn't go through, an action that errored out. A low or zero error rate is what you want. A rising error rate means real users are hitting problems right now.

Latency

How fast your app responds — in plain terms, how slow it feels to your users. Low latency means snappy. High latency means people are waiting, which usually feels like the app is "being slow" even when nothing is technically broken.

Traffic

How much is happening — roughly, how many people are using your app. This is your sense of scale: a quiet morning, a sudden spike, or a steady flow. On its own it's not good or bad, but it gives the other three numbers context.

When something looks wrong

If a signal goes red, you don't fix it from here — the overview tells you that something's off, and the logs tell you what. Head to your logs to search for the specific error and trace exactly what happened.

Watching your app here changes nothing about how it runs. The overview only reads and reports — looking at it can't break anything.

Where to go next

• Logs — search and filter everything your app records to find the cause of a problem.
• Database schema — see the live structure of the data your app is storing.
• Stages — view these signals separately for Production, Development, and Preview.