> For the complete documentation index, see [llms.txt](https://docs.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neevcloud.com/neevcloud-products/monitoring/pulse-monitoring.md).

# Pulse Monitoring

NeevCloud Monitoring (Pulse) watches your servers and websites and alerts you when something needs attention.

A lightweight agent on each server reports metrics to NeevCloud, and an alert is raised when a reading crosses a defined threshold.

### What It Monitors

* **Servers (Linux and Windows):** CPU, memory, disk, swap, network, uptime, processes, logged-in accounts and OS details.
* **Websites:** Availability and response time of a URL.

### Requirements

* A NeevCloud account.
* Admin or root access on each server you want to monitor.

### Accessing Pulse Monitoring

Pulse Monitoring is available from the NeevCloud console. No separate login is required.

1. Sign in to [my.neevcloud.com](https://my.neevcloud.com).
2. In the left sidebar, under **More**, select **Pulse Monitoring**.
3. The monitoring dashboard opens, signed in with your NeevCloud account.

<figure><img src="https://1876135298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEC5NwtFshv6EATOemuUn%2Fuploads%2F8yaat6280gSW0mhCnk9g%2Fimage.png?alt=media&amp;token=269f80a5-af4f-420f-be37-3cb676605a60" alt=""><figcaption></figcaption></figure>

### Adding a Server

#### Step 1: Register the Server

1. Open **Add host** from the sidebar and keep the **Server** tab selected.
2. Enter a display name for the server.
3. Select **Linux** or **Windows**.
4. Keep the connection mode set to **Active**.
5. Click **Add host**. The install command is displayed.

<figure><img src="https://1876135298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEC5NwtFshv6EATOemuUn%2Fuploads%2FzntbzPSLfZV1Iec8VXJp%2Fimage.png?alt=media&amp;token=1da2b944-06b1-4e90-83d8-c1d912061a03" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1876135298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEC5NwtFshv6EATOemuUn%2Fuploads%2Fuzn144wH7suVAHrEwU4N%2Fimage.png?alt=media&amp;token=f898441f-deaf-4e62-bf69-10bf7001afa8" alt=""><figcaption></figcaption></figure>

#### Step 2: Run the Install Command

**Linux** (run as root or with sudo):

```bash
curl -fsSL "https://pulse.neevcloud.com/bootstrap/linux/..." | sudo bash
```

**Windows:** Right-click **Start**, select **Terminal (Admin)**, and paste the command.

> **Note:** Paste the command directly into PowerShell. Do not wrap it in `powershell -Command "..."`, as security software may block it.

Installation takes less than a minute. Data appears on the dashboard within one to two minutes.

#### Connection Modes

* **Active (default):** The agent connects out to NeevCloud. No firewall changes or fixed IP are required.
* **Passive:** NeevCloud connects to your server. Requires a server IP and port `10050` to be reachable. The installer opens the local firewall; external firewalls must be configured by you.

Use Passive mode only if your security policy requires it.

#### Install Command Validity

The install command is shown once and expires after **7 days**. If it is lost or expired, contact NeevCloud support for a new one. The host keeps its history and settings.

### Adding a Website

Website monitoring checks that a URL is reachable and records its response time. No agent is required.

1. Open **Add host** and select the **Website** tab.
2. Enter a display name and the full URL, including `http://` or `https://`.
3. Click **Add host**. The first check runs within a few minutes.

The host page shows response time and, for HTTPS sites, the SSL certificate expiry date.

**Not supported:** Private and internal addresses (loopback, private IP ranges, link-local and cloud metadata endpoints). To monitor an internal service, monitor the server it runs on.

Each website uses one host slot.

<figure><img src="https://1876135298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEC5NwtFshv6EATOemuUn%2Fuploads%2F8CVJ9npTXoxTItpAePhx%2Fimage.png?alt=media&amp;token=717648e5-d0c9-460d-a4a9-c13627fa9303" alt=""><figcaption></figcaption></figure>

### Server Dashboard

Select a host from **Hosts** to open its page.

* **Status bar:** Shows the current state of the server. Session count reflects login sessions, not individual users.
* **Metric cards:** CPU, memory, disk, swap, uptime and network. Values turn amber, then red, as they approach critical levels. Load average is shown for Linux only.
* **Live trend:** Chart any metric over a period from one hour to one month.
* **Active problems:** Alerts currently raised on the host.
* **All metrics:** Every reading, grouped by category.

Network interfaces, OS details and agent version are collected hourly and may show "not collected yet" on a new server.

<figure><img src="https://1876135298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEC5NwtFshv6EATOemuUn%2Fuploads%2FUCIJ4IlrCRUTngcNmFsM%2Fimage.png?alt=media&amp;token=c2b15f2f-2b5c-4a99-8a6d-a84a7ddaf0d8" alt=""><figcaption></figcaption></figure>

### Alerts

All active alerts are listed under **Alerts** in the sidebar, newest first. Each host page also shows its own alerts.

**Severity levels:** Not classified, Info, Warning, Average, High, Disaster.

#### Acknowledge and Clear

* **Acknowledge:** Marks the alert as seen. Use this while you investigate the issue.
* **Clear:** Closes the alert. If the issue still exists, the alert returns within about a minute.

To stop an alert from appearing permanently, mute it from **Alert filtering**.

<figure><img src="https://1876135298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEC5NwtFshv6EATOemuUn%2Fuploads%2FM6ixcQHUXmRtjzvpRlxO%2Fimage.png?alt=media&amp;token=fd484f45-4a00-48ad-8828-38f4f2710906" alt=""><figcaption></figcaption></figure>

#### Alert Conditions

Most alerts require a condition to persist over time. For example, "above 90% for 5 minutes" means every reading during those 5 minutes must exceed 90%. Short spikes do not trigger alerts.

Example condition:

```
min(/system.cpu.util,5m)>90
```

### Default Checks

Every server is monitored automatically once the agent is installed.

**Linux and Windows:**

* Agent not reporting
* Sustained high CPU or memory usage
* Low available memory
* Low disk space or inodes
* Swap usage
* Server restart
* Slow disks

**Linux only:** Load average and open file/process limits.

**Windows only:** Stopped auto-start services and Windows-specific CPU and memory counters.

The full list of checks, with conditions and severities, is available under **Help and FAQ** in the dashboard.

Default thresholds cannot be edited. To use a different threshold, create a custom alert.

### Alert Filtering

Go to **Settings → Alert filtering**. Filters apply to both the Alerts page and notifications.

* **Minimum severity:** Hides and stops sending alerts below the selected level.
* **Muting:** Hides any alert whose name contains the entered text. Matching is case-insensitive and applies to all hosts.
* **Severity overrides:** Changes the severity of alerts that match the entered text.

### Custom Alerts

1. Select the host.
2. Select **CPU usage** or **Memory usage**.
3. Enter a threshold percentage (minimum 10%).
4. Select the duration.
5. Select a severity and click **Add**.

* One custom rule is allowed per metric per host.
* Custom rules apply in addition to default checks.
* Only CPU and memory are supported.

### Notifications

Alerts always appear on the dashboard. Notification channels deliver them to you through other services.

1. Open **Notifications** from the sidebar.
2. Select a channel type and enter the required details.
3. Save the channel. A test message is sent immediately; the channel is saved only if the test succeeds.

> **Note:** Email notifications are currently disabled platform-wide.

* **Custom webhooks:** A JSON payload with the message, source and timestamp is sent. An optional shared secret is sent in the `X-NeevCloud-Secret` header. The endpoint must use public HTTPS.
* **Filtering:** Only alerts that pass your alert filters are sent.
* **Credentials:** Tokens and webhook URLs are encrypted and masked after saving. To change them, delete and re-add the channel.

### Team Access

Go to **Settings → Who has access**.

* **Invite:** Enter the user's email and select a role. The user appears as Pending until they accept.
* **Access:** Members can view everything in the account they were invited to.
* **Remove:** Removing a member ends their access immediately.

Team members share the account's host limit.

### Maintenance Windows

Use maintenance windows to suppress alerts during planned work.

1. Open the host page.
2. In the maintenance panel, click **Schedule maintenance**.
3. Select a duration (1, 2, 4, 8 or 24 hours) and confirm.

During maintenance, alerts are suppressed and metrics continue to be collected. Any problem still present after the window ends is raised as normal. You can cancel a window early from the same panel.

### Health Reports

Health reports provide a plain-language summary of a server's performance.

1. Open the host page.
2. Under **Health Report**, select **Weekly** or **Monthly**.
3. Click **View report** or **Download**.

Each report includes uptime, average and peak resource usage, outages with duration, and key observations. Downloaded reports are standalone HTML files that can be opened in any browser.

### Host Limit

Each account can register up to **20 hosts**. Servers and websites count towards the same limit, shared across all team members.

* **Check usage:** The Add host page shows the number of hosts used.
* **Increase the limit:** Contact NeevCloud support.
* **Free a slot:** Delete a host.

Deleting a host removes its history but does not uninstall the agent from the server.

### Removing the Agent

Run the following command on the server to uninstall the agent.

**Linux:**

```bash
curl -fsSL "https://pulse.neevcloud.com/bootstrap/uninstall/linux" | sudo bash
```

**Windows** (PowerShell as Administrator):

```powershell
Set-ExecutionPolicy Bypass -Scope Process -Force; iwr -useb 'https://pulse.neevcloud.com/bootstrap/uninstall/windows' | iex
```

This removes the agent, its configuration, the machine's identifying key and the firewall rule for port `10050`. No other system changes are made.

### Support

For help with Pulse Monitoring, raise a ticket from the **Support** section in the dashboard.