Status Dashboard
A status dashboard is a single screen that shows the current health of everything you monitor. The MonitorUrs dashboard displays the real-time up or down status of your website and API probes alongside the live metrics of your servers, so you can confirm at a glance whether everything is healthy.
Last updated: June 2026
Why a single dashboard matters
When your infrastructure spans multiple servers, websites and APIs, the hardest question to answer quickly is also the simplest one: is everything okay right now? Checking each system separately is slow, error-prone and easy to skip when you are busy. A problem on one server or a single down endpoint can hide in plain sight if you have no central place to look.
A status dashboard solves that by gathering everything into one view. Instead of jumping between tools and tabs, you open one screen and immediately see what is up, what is down and which servers are reporting trouble. That shared picture is what lets a team react fast, prioritise the right fire, and stay confident that nothing is quietly broken in the background.
What the MonitorUrs dashboard shows
The MonitorUrs dashboard is a web app that brings together the current state of everything you monitor in one place. It pulls together several kinds of information:
- Probes — your websites, APIs and HTTP endpoints, each shown with its current up or down status so you can see availability at a glance.
- Servers — every machine running the MonitorUrs agent, with its live metrics and an online or offline indicator based on the last time it reported in.
- Drives — disk and drive usage reported by each server agent, so you can spot a volume that is filling up before it causes an outage.
- Processes — the running processes reported by the agent, giving you visibility into what is actually consuming resources on a server.
- Current incidents — any probe that is down or server that is offline right now, surfaced so the things that need attention are easy to find.
Because the dashboard reflects current states and recent check results, what you see is the latest reported status rather than a stale report you have to refresh manually.
Real-time server and website status at a glance
Probes and servers are two different kinds of monitoring, and the dashboard surfaces the right details for each. A probe answers "is this endpoint responding correctly?", while a server answers "is this machine healthy and how hard is it working?" The table below shows what the dashboard surfaces for each.
| What the dashboard surfaces | For probes (websites & APIs) | For servers (agent metrics) |
|---|---|---|
| Live status | Up or down based on the latest check. | Online or offline based on the last-seen time. |
| Core signal | HTTP response and recent check results. | CPU, memory, disk/drive usage and network throughput. |
| Detail view | Recent results for that endpoint. | Running processes reported by the agent. |
| Freshness | Time of the most recent check. | Last-seen time the agent reported in. |
| On the dashboard | Flagged immediately when a probe is down. | Flagged immediately when a server goes offline. |
The dashboard supports both light and dark mode, so you can keep it open on a screen all day in whichever theme is easiest on your eyes. Whether you are tracking a handful of sites or a fleet of servers, the goal is the same: one place that tells you the truth about your systems right now.
From dashboard to alert to history
The dashboard does not work in isolation — it is the real-time face of a single underlying record. When a check fails, three things describe the same event from different angles:
- The dashboard shows the change immediately, flipping a probe to down or a server to offline so anyone watching sees it.
- The alert reaches the right people through Telegram, SMS or Email, so you find out even when you are not looking at the screen.
- The incident history records the event with its timeline, so later you can review exactly what happened and for how long.
That means a status change you spot on the dashboard is the same event that fires an alert and lands in your incident history. The dashboard gives you the "now", and the history gives you the "what happened" — together they cover both the immediate response and the longer-term record.
Use cases
- NOC and operations teams — keep the dashboard open as the team's single source of truth, so anyone glancing at it can tell instantly whether the environment is healthy.
- On-call engineers — when an alert fires, open the dashboard to see the wider context: is this one probe, or is a whole server offline and taking several endpoints with it?
- Agencies managing many clients — watch every client's sites and servers from one dashboard instead of logging into each one separately, and use the history to prove uptime.
- Small teams and solo operators — get the assurance of a central overview without standing up a complex monitoring stack of your own.
How it fits with incident history and alerting
The status dashboard is the central view in a complete monitoring strategy. It draws on the same data as uptime monitoring for availability, response-time monitoring for performance, and website monitoring for your public-facing pages. Every probe check and server report feeds the real-time overview, and each status change is preserved in your incident history for the long-term record. The dashboard shows you what is happening now; the history and alerts make sure nothing is missed or forgotten.
Frequently asked questions
What is a status dashboard?
A status dashboard is a single screen that shows the current health of everything you monitor. The MonitorUrs dashboard displays the real-time up or down status of your probes and the live metrics of your servers, so you can see whether everything is healthy at a glance.
Is the MonitorUrs dashboard updated in real time?
Yes. The dashboard reflects the current state of your probes and servers and shows recent check results, so the status you see is the latest reported state rather than a stale snapshot.
What does the MonitorUrs dashboard show for servers?
For each server the dashboard shows live metrics reported by the agent, including CPU, memory, disk and drive usage, network throughput and running processes, along with the last-seen time and an online or offline status.
Can I see active incidents on the dashboard?
Yes. The dashboard surfaces current incidents alongside your probes and servers, so any probe that is down or any server that is offline is visible immediately. From there you can open the incident history to see the full timeline.
Does the dashboard support dark mode?
Yes. The MonitorUrs dashboard supports both light and dark mode, so you can keep it open on a screen all day in whichever theme is easiest on your eyes.
How does the dashboard relate to incident history and alerts?
The dashboard is the real-time overview, alerts notify you the moment a check fails, and the incident history keeps the long-term record. A status change you see on the dashboard is the same event that triggers an alert and is recorded in the incident history for later review.