Health

The platform home page - a management overview, a ranked analysis of what needs attention across all your hosts, and the live alerts behind it.

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.

The page has three parts, top to bottom:

  • Management overview - the decisions to take.
  • Analysis - the ranked technical problems.
  • The alert columns - the live checks that are firing.
The Health page with the Management overview, the Analysis card with its severity filters, and the alert columns
The Health page with the Management overview, the Analysis card with its severity filters, and the alert columns

Management overview

The Management overview at the top summarizes the state of your hosts in business terms, so you can decide without reading every alert. It appears once the platform has analyzed your hosts. Until then the page starts with the Analysis.

  • A status badge: Critical, Needs attention, Stable or Awaiting analysis.

  • A short executive summary, or "Showing highest-severity decisions from N total".

  • Decision cards, one per recommended decision. Each has an urgency (Now, 7 days, 30 days or Monitor), a severity, an optional opportunity badge, and Customer: and Server: chips. Selecting its action (... · Evidence) expands and highlights the matching entry in the Analysis, so you can read the technical evidence behind the decision.

  • Show N more reveals further decisions, three at a time.

  • Accounts that manage several customers get an All customers tab and one tab per customer.

  • The footer shows the age of the latest and the oldest host analysis, and warns when some customer data could not be loaded.

The search box does not narrow the overview. It narrows the Analysis and the alert columns.

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 a severity (Critical, High, Medium or Low) and a category such as AVAILABILITY, PERFORMANCE or STABILITY. A link chip names each host or cluster it affects. An Open badge marks a problem that is still active. Entries are sorted by severity, then by rank.

Select an entry to expand it in place. The expanded entry shows the event count of the last 30 days, the critical count, the number of active days and the alarming services. Then come What happens and the Recommended fix. Below that, Investigated reports lists the reports written about it. Open report opens one in a window with a Link button, which copies an address that opens the same report, and a PDF button.

Go to host opens the affected server. For a cluster this reads Go to cluster. The button is shown only when the problem maps to a single host or cluster.

The severity checkboxes inside the card (Critical, High, Medium, Low) narrow the list. Several can be selected at once, and Clear resets them. Search host name narrows the Analysis and the alert columns to matching hosts and clusters. Both are part of the page address, so a filtered view can be bookmarked.

When nothing is known yet, the card reads "No top issues found for your hosts."

The alert columns

Below the analysis are the live monitoring alerts: the individual checks that are firing right now. Not every problem check is listed. The columns show what needs a person:

  • Alerts - checks in a confirmed CRITICAL state that carry a priority P1 to P4, ordered by priority.

  • Mail Problems - Warning and Critical checks about email.

  • Security Issues - confirmed critical checks in the security category, for example hosts with security or system packages still to update.

Checks that were acknowledged or fall in a planned downtime are not shown. The state filter (Critical, Warning, Unknown) narrows the columns and Clear filters resets it. The columns say "No alerts match your search or state filter." when nothing is left.

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 alert detail page for that check. The host name in the row is a separate link and opens the host. For a cluster member it opens the cluster. The page refreshes as new alerts arrive and shows when it last updated.

When nothing is wrong, the page reports All clear instead of empty columns.

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, swap and Disk graphs on a host's Health tab, which open it in a new browser tab. A host you have no access to returns "not found".

The alert detail page for a swap check, with the Status, Graph and Incident reports panels and the Create ticket button
The alert detail page for a swap check, with the Status, Graph and Incident reports panels and the Create ticket button

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 output
  • Graph - the measured values over time
  • Incident reports - reports written about this check
  • Create a ticket - hand the alert over to support

Select a panel header to collapse or expand it.

Status

A badge next to the panel title shows the current state: OK, WARNING, CRITICAL or UNKNOWN. The panel lists:

Field What it tells you
Since How long the check has been in this state, with the date and time it changed.
Groups The monitoring groups this check belongs to.
Plugin Output The message the check returned. It usually names the exact problem, for example a filesystem that is nearly full or a certificate that is about to expire.

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.

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. Its Link button copies an address that opens this page with the report already open. The button confirms with Copied. 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:

Metric What it means
CPU How busy the processor is. Sustained high values mean the host is CPU-bound.
RAM Used memory, with the extra capacity TurboRAM adds. Consistently high RAM with rising swap points to memory pressure.
Disk Swap Usage Memory spilled to the swap file on disk. Steady use of it is what hurts performance.
Disk How full each filesystem is. A full disk causes failures; act before it fills.

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 in the Alerts column carry a priority from P1 (most urgent) to P4, and the column is ordered by it.

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).

© 2026 Hosted Power — TurboStack