You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Support/monitoring.md
+6-18Lines changed: 6 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,33 +7,21 @@ icon: zoom-in
7
7
8
8
## Proactive monitoring
9
9
10
-
At **Hosted Power**, we recognize the paramount importance of application availability and stability to our partners. Our comprehensive approach to ensuring stability encompasses various factors, chief among them being the reliability of the TurboStack platform itself. With our dedicated team of experts vigilantly monitoring your environments round the clock, 7 days a week, rest assured that your application's stability is our top priority.
11
-
12
-
Should any threat arise, our skilled engineers are on standby to swiftly intervene, safeguarding your operations seamlessly.
10
+
At **Hosted Power**, application availability and stability are a top priority for our partners. Our team monitors your environments around the clock, 7 days a week, so issues are caught early. Should a problem arise, our engineers are on standby to intervene quickly and keep your application running.
13
11
14
12
You can follow the same checks yourself in the TurboStack platform: the [Monitoring dashboard](../TurboStack%20Platform/monitoring.md) gives a fleet-wide overview of every open alert, while the per-host [Health tab](../TurboStack%20Platform/Hosts/health.md) shows the detailed status of an individual server.
15
13
16
14
## Alerting
17
15
18
-
In critical situations , Hosted Power activates its On Call procedure. Our on call team is on standby 24/7, ensuring swift manual investigation and resolution of issues, regardless of office hours. If the primary On Call colleague doesn’t respond within 30 minutes, an alert automatically triggers escalation to the entire on call team, engaging our Operations engineers on call "pool" until someone acknowledges the issue en starts to research.
16
+
In critical situations, Hosted Power activates its on-call procedure. Our on-call team is on standby 24/7, ensuring swift manual investigation and resolution of issues, regardless of office hours. If the primary on-call colleague does not respond within 30 minutes, the alert automatically escalates to the entire on-call team, engaging our Operations engineers until someone acknowledges the issue and starts investigating.
17
+
18
+
Once alerted, the on-call colleague tackles the issue, whether that involves freeing up disk space, restarting services, or mitigating abusive traffic. If necessary, the issue is escalated to our cloud providers for matters unrelated to **Hosted Power**.
19
19
20
-
Once alerted, our On Call colleague tackles the issue, whether it involves tasks like disk space optimization, restarting services, or mitigating abusive traffic. If necessary, escalation to our cloud providers occurs for issues unrelated to **Hosted Power**.
20
+
## Escalation matrix
21
21
22
-
## Escalation Matrix
23
-
This matrix shows how our escalation processes take place.
22
+
This matrix shows how our escalation process works.
24
23
25
24
### Escalation of customer contacts
26
25
* Operations engineer (technical) or account manager (commercial)
27
-
* (Servicemanager) if applicable
28
-
* Operations manager
29
26
* Technical Team Lead (technical problems) or COO (commercial problems)
Copy file name to clipboardExpand all lines: TurboStack Platform/Hosts/health.md
+29-28Lines changed: 29 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,75 +3,76 @@ order: 50
3
3
icon: pulse
4
4
---
5
5
6
-
# Health - server health and monitoring overview
6
+
# Health - server monitoring and status overview
7
7
8
-
The **Health** tab is your **first stop** when opening a host. It provides a **real-time overview** of the server's condition, surfaces the most important **alerts**, and gives you direct access to detailed monitoring **reports** and **services**.
8
+
The **Health** tab is your first stop when opening a host. It provides a real-time overview of the server's condition, surfaces the most important alerts, and gives you direct access to detailed monitoring reports and services.
Unlike the fleet-wide [Monitoring dashboard](../monitoring.md), the Health tab is fully **scoped to a single host**, giving you **deep insight** into how this specific server and its applications are behaving right now and over time.
12
+
Unlike the fleet-wide [Monitoring dashboard](../monitoring.md), the Health tab is scoped to a single host, showing how this specific server and its applications are behaving right now and over time.
13
13
14
-
What makes the Health tab particularly powerful is that it does not just **show the status** of your server - it actively helps you **resolve issues**. For every entry in**Top Issues** and every report under **Latest Reports**, the TurboStack platform provides a **detailed analysis** of the underlying problem, together with **concrete, context-aware recommendations** on how to fix it. This turns the Health tab from a passive status page into an **actionable troubleshooting tool**, helping you move from *"something is wrong"* to *"here is exactly what to do about it"* in a single click.
14
+
The Health tab does more than show status: for every entry under**Top Issues** and every report under **Latest Reports**, the TurboStack platform adds an analysis of the underlying problem together with recommendations on how to fix it.
15
15
16
-
This page describes every section of the Health tab and how to use it to keep your infrastructure running smoothly.
16
+
The tab is divided into four areas, each described below:
17
+
18
+
-**[Host Monitoring](#host-monitoring)** (top right) - live CPU, RAM and disk usage.
19
+
-**[Top Issues](#top-issues)** (top left) - the most important active alerts on the server.
20
+
-**[Latest Reports](#latest-reports)** - a chronological list of health reports for the server and its applications.
21
+
-**[Services](#services)** (bottom) - the full list of monitored services and their current status.
17
22
18
23
## Host Monitoring
19
24
20
-
The **Host Monitoring** panel, located on the top right, displays the most important **resource metrics** of your server at a glance:
25
+
The **Host Monitoring** paneldisplays the most important resource metrics of your server at a glance:
21
26
22
27
-**CPU Usage** - the current CPU load, accompanied by a graph showing the `load1` average over time.
23
28
-**RAM Usage** - the current memory consumption, with a detailed breakdown of used, free, cached, warning and critical thresholds.
24
29
-**Disk Usage** - the current disk consumption on the root filesystem, plotted against warning and critical thresholds.
25
30
26
-
Each metric is shown as a percentage, combined with a colour-coded **status indicator** (OK, Warning, Critical) so you can immediately spot any resource that needs attention.
31
+
27
32
28
-
33
+
Each metric is shown as a percentage, combined with a colour-coded status indicator (OK, Warning, Critical) so you can immediately spot any resource that needs attention.
29
34
30
35
### Timeframe selector
31
36
32
-
In the top right corner of the Host Monitoring panel, you can switch the timeframe of the graphs between **1H**, **8H**, **1D** and **7D**. This allows you to quickly **zoom in** on a recent spike or **zoom out** to identify longer-term trends in resource usage.
37
+
In the top right corner of the panel, you can switch the timeframe of the graphs between **1H**, **8H**, **1D** and **7D**. This lets you zoom in on a recent spike or zoom out to spot longer-term trends in resource usage.
33
38
34
39
!!! info
35
-
The Host Monitoring graphs are based on the same data used by our 24/7 monitoring system. If a metric crosses a critical threshold, our team will be alerted automatically.
40
+
The Host Monitoring graphs are based on the same data used by our 24/7 monitoring system. If a metric crosses a critical threshold, our team is alerted automatically.
36
41
!!!
37
42
38
43
## Top Issues
39
44
40
-
The **Top Issues** panel, on the top left, lists the **most important active alerts** on your server right now. Each issue is tagged with a **category** (e.g. `AVAILABILITY`, `STABILITY`, `PERFORMANCE`) and a **status** (e.g. `Open`).
45
+
The **Top Issues** panellists the most important active alerts on your server right now. Each issue is tagged with a category (e.g. `AVAILABILITY`, `STABILITY`, `PERFORMANCE`) and a status (e.g. `Open`).
41
46
42
-
47
+
43
48
44
-
Clicking an issue **expands** it, revealing:
49
+
Clicking an issue expands it to reveal:
45
50
46
-
1. A **detailed description** of the problem, including the affected service and the impact on your environment.
47
-
2. A **proposed solution** suggested by the TurboStack platform, based on the type of issue and the server's configuration.
51
+
1. A detailed description of the problem, including the affected service and the impact on your environment.
52
+
2. A proposed solution suggested by the TurboStack platform, based on the type of issue and the server's configuration.
48
53
49
-
This makes it easy to understand **what is wrong**, **why it matters**, and **what to do next**, without having to dig through logs or external dashboards.
54
+
This makes it easy to understand what is wrong, why it matters, and what to do next, without having to dig through logs or external dashboards.
50
55
51
56
## Latest Reports
52
57
53
-
Below the Top Issues panel, the **Latest Reports** section provides a chronological list of **detailed health reports** generated for the server and its applications.
54
-
55
-
58
+
The **Latest Reports** section, below Top Issues, provides a chronological list of detailed health reports generated for the server and its applications.
56
59
57
-
Each report is linked to a specific check (e.g. `rabbitmq-online`, `postgres-online`, `website`) and includes the **severity level** (e.g. `P1 CRITICAL`), the **affected host or URL** and the **time the report was generated**.
60
+
58
61
59
-
Click **Open report** on any entry to view the full report, including timestamps, related metrics and historical context. This is particularly useful when investigating **incidents** or preparing a **post-mortem**.
62
+
Each report is linked to a specific check (e.g. `rabbitmq-online`, `postgres-online`, `website`) and includes the severity level (e.g. `P1 CRITICAL`), the affected host or URL and the time the report was generated. Click **Open report** on any entry to view the full report, including timestamps, related metrics and historical context. This is particularly useful when investigating incidents or preparing a post-mortem.
60
63
61
64
## Services
62
65
63
-
At the bottom of the Health tab, the **Services** panel shows a complete list of every **monitored service** on the server, together with its current **status** and the **latest check output**.
The **Services** panel, at the bottom of the tab, shows a complete list of every monitored service on the server, together with its current status and the latest check output. For each service you will see:
- The **status** (`OK`, `WARNING`, `CRITICAL`, `UNKNOWN`).
71
70
- The **plugin output**, which contains the raw result of the check (e.g. response times, free disk space, error messages).
72
71
- The **timestamp** of the most recent check.
73
72
74
-
This view gives you an exhaustive overview of **everything we monitor** on your server, making it easy to confirm that all services are healthy or to drill down into a specific check that is failing.
This view gives you a complete overview of everything we monitor on your server, making it easy to confirm that all services are healthy or to drill down into a specific check that is failing.
75
76
76
77
!!! info
77
78
If a service is in an `UNKNOWN` or `CRITICAL` state and you are not sure how to resolve it, please contact our [Support](../../Support/standard_support.md) team. Our engineers have access to the same monitoring data and can intervene 24/7. See our [24/7 monitoring and alerting](../../Support/monitoring.md) overview for how this works.
0 commit comments