Health
Health is the platform's home page: signing in takes you here. It gives you a fleet-wide view of what needs attention across all your hosts, so you can spot problems without opening each host individually. For teams running business-critical sites, this helps you notice and react quickly - for example during a busy campaign - before visitors are affected.
It is reachable from Health in the sidebar, at /monitoring. The same view for a single server
is that host's Health tab.
Analysis: what to look at first
The Analysis card is the ranked list of problems TurboStack has identified across your hosts, most important first. It is not a raw alert feed: each entry is a described problem, with the host it affects, a severity (Critical, High, Medium or Low) and a category such as AVAILABILITY, PERFORMANCE or STABILITY.
Each entry offers:
-
Open report - the full analysis, with What happens and a Recommended fix, plus how many days the issue has been active and how many events it covers.
-
Go to host - opens the affected server. For a cluster this reads Go to cluster.
Use the counters above the card (Critical, High, Medium, Low) to filter to one severity, and Search host name to narrow everything on the page to one server. Clear removes the filters.
The alert columns
Below the analysis are the live monitoring alerts themselves - the individual checks currently in a non-OK state. They are split into columns, the main one being Alerts (server and application checks), alongside others when they apply, such as Security Issues (hosts with security or system packages still to update) and mail-specific problems.
Alerts carry a priority badge - from P1 (most urgent) down to P4 - and their own state filter: Critical, Warning and Unknown.
Each alert names the affected host and service (for example a disk, swap, certificate, or
cache-hit-ratio check) with a short status message and how long it has been active. Selecting an
alert row opens the
When nothing is wrong, the page reports All clear instead of empty columns.
Tip
Start with Analysis, not with the alert columns. The analysis groups related alerts into one described problem and ranks them, so it tells you what to do; the columns tell you what is firing.
The alert detail page
Selecting an alert opens a page for that one service check, at /monitoring/<host>!<check>. The
heading shows the host name followed by the check name, and the host name links to the host. You
also reach this page from the CPU, RAM and Disk graphs on a host's Health tab,
which open it in a new browser tab.
The page reads the current state from monitoring every time you open it. It has three panels and one action:
Status - the current state and the check outputGraph - the measured values over timeIncident reports - reports written about this checkCreate a ticket - hand the alert over to support
Select a panel header to collapse or expand it.
Note
If the check no longer exists in monitoring, the page reports that it cannot be found. Go back to the dashboard and pick a current alert.
Status
A badge next to the panel title shows the current state: OK, WARNING, CRITICAL or UNKNOWN. The panel lists:
Each field is shown only when there is a value for it.
Graph
The Graph panel plots what the check measured. Use the 1H / 8H / 1D / 7D buttons to change the time range, from one hour to seven days. The panel is not shown for checks that record no measurements, such as a check that only reports a state.
Tip
Compare the 1-hour and 7-day views before you act. A single short spike is usually harmless; a line that climbs day after day needs attention.
Incident reports
When incident reports exist for this host and check, they are listed here, with the number of reports next to the panel title. Each entry shows the report title, the alarm it relates to, and how long ago it was written.
- Open report shows the full report in a window on top of the page.
- PDF opens the same report as a Portable Document Format (PDF) file in a new browser tab, where you can read or save it. The button appears only when a PDF version exists.
The report window has the same PDF button in its header. Select Close or the cross in the header to return to the alert.
Create a ticket
Create ticket, at the top right of the page, opens the Hosted Power ticket portal in a new browser tab. The subject is filled in with the host name and the check, so you do not have to retype it. Use it when an alert needs follow-up from the support team - see Support.
Per-host health
For the live health of a single host - top issues, CPU/memory/disk usage and individual service checks - open that host's Health tab.
Understanding the metrics
The per-host view (and the Health tab) report four core resource metrics:
Note
The memory graphs include the extra capacity that TurboRAM provides, so a server can report more effective memory than it has physical RAM. That is expected.
Each service the host runs (web server, databases, Redis, search, mail, certificates, and more) is also checked individually and reports OK / Warning / Critical.
Alert priorities
Alerts are grouped by priority so you can triage quickly:
Important
Not every alert is equally urgent, and not all of them need action. Triage them in order:
- P1 and P2 first - these affect, or are about to affect, your live sites. Act on them right away.
- P3 next - look at these when you have time; usually a trend to watch rather than an outage.
- P4 is optional - informational only, fine to review during normal maintenance.
Working top-down (P1 first) keeps your attention on what actually impacts visitors.
Alerts are also grouped by type, such as Mail Problems and Other. Hosted Power's team monitors these alerts; follow up through Support for anything affecting your sites.
How monitoring works
TurboStack monitors your infrastructure and applications, and can integrate application performance monitoring. For the underlying tools and what each provides, see Monitoring (concepts).
Related
- Health (per host)
- Threat Center - the same fleet-wide view for security findings
- Monitoring concepts
- What is TurboRAM?
- Support
- Hosts