> ## Documentation Index
> Fetch the complete documentation index at: https://docs.areawp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring

> System-wide resource monitoring with configurable thresholds, alert history, email/webhook notifications, and public status pages.

<Warning>
  This feature is **available on the Hosted plan only**. On the self-hosted version, server monitoring is managed directly on the server without this interface.
</Warning>

<Info>
  **Path:** Monitoring (`/monitoring`) → Status Pages (`/status-pages`) — Admin only
</Info>

## Stats Overview

Four cards at the top of the Monitoring page:

| Card                     | Shows                                        |
| ------------------------ | -------------------------------------------- |
| **Monitoring Status**    | Active or Inactive                           |
| **Recent Alerts**        | Count of alerts in the last 24 hours         |
| **Check Interval**       | How often the system polls metrics (seconds) |
| **Notification Methods** | Email and/or webhook configured              |

Below the cards: current threshold values for CPU, memory, disk, and load average.

***

## Tabs

### Overview

High-level health summary: stat cards, current threshold display, and a preview of the 5 most recent alerts (with severity icons).

### Alert History

Full alert log with severity filter buttons:

| Filter       | Shows                                 |
| ------------ | ------------------------------------- |
| **All**      | Every alert                           |
| **Critical** | Thresholds exceeded at critical level |
| **Warning**  | Thresholds exceeded at warning level  |
| **Info**     | Informational events                  |

**Alert table columns:** Severity icon/badge, Alert type, Message, Current value, Threshold, Timestamp.

### Configuration

| Setting               | Description                                   |
| --------------------- | --------------------------------------------- |
| **Enable monitoring** | Toggle to start/stop the monitoring agent     |
| **Check interval**    | Polling frequency (10–3600 seconds)           |
| **Email**             | Auto-synced to your account email — read-only |
| **Webhook URL**       | HTTP endpoint to receive alert POSTs          |

**Test buttons** for both email and webhook let you verify delivery before going live.

<Warning>
  If SMTP is not configured in Settings, the email notification field shows a warning. Set up SMTP under **Settings → Email** first.
</Warning>

### Thresholds

Set warning and critical thresholds using dual-range sliders for:

* **CPU usage** (%)
* **Memory usage** (%)
* **Disk usage** (%)
* **Load average**

Changes save on form submit. Current values are shown as a reference display in the Overview tab.

***

## Status Pages

**Path:** `/status-pages`

Create public-facing status pages to communicate uptime and incidents to clients.

### Creating a Status Page

1. Go to **Monitoring → Status Pages → New Status Page**
2. Set a name, slug (URL), and optional custom domain
3. Add components — each component maps to a service or uptime check
4. Configure visibility (public or link-only)
5. Customize branding (logo, colors)

### Component Statuses

| Status               | Color  |
| -------------------- | ------ |
| ✅ Operational        | Green  |
| ⚠️ Degraded          | Yellow |
| 🔴 Partial Outage    | Orange |
| ❌ Major Outage       | Red    |
| 🔧 Under Maintenance | Blue   |

### Incidents

Create an incident to communicate an ongoing issue:

* Choose affected components and severity
* Write an update message
* Subscribers are notified immediately by email

Post follow-up updates as the incident progresses. Mark **Resolved** when fixed.