Netdata Installation & Monitoring Guide for VPS

🚀 Step 1: Start from Local SSH

1. Open your terminal.
2. Connect to your VPS via SSH:

ssh root@<your-vps-ip>

Example:

ssh root@<your-vps-ip>

🔥 Step 2: Install Netdata on VPS (Ubuntu - Hostinger VPS)Run the official kickstart script:

bash <(curl -Ss https://my-netdata.io/kickstart.sh)

︎ This installs the latest Netdata (nightly or stable based on availability).

🔗 Step 3: Access Netdata UI👉 Option 1: Direct Access (Not recommended for public IP)

• Open in your browser:

http://<your-vps-ip>:19999

Example:

http://<your-vps-ip>:19999

👉 Option 2: 🚀 Secure Access via SSH Tunneling (Recommended)

Run this command from your local machine:

ssh -L 19999:localhost:19999 root@<your-vps-ip>

Example:

ssh -L 19999:localhost:19999 root@<your-vps-ip>

→ Then open in your browser:

http://localhost:19999

🔒 This forwards the remote Netdata port securely to your local machine.

🔍 Debugging & Monitoring Tips✅ Check if Netdata is Running:

sudo systemctl status netdata

✅ Restart Netdata:

sudo systemctl restart netdata

✅ Check Plugin Health:

sudo /usr/libexec/netdata/plugins.d/go.d.plugin -m

︎ Lists loaded modules.

✅ Check Logs:

sudo journalctl -u netdata --since "10 minutes ago"

or Netdata error logs:

sudo cat /var/log/netdata/error.log

⚙️ Netdata Useful Monitoring Sections:

• CPU Utilization → Detect saturation.
• RAM Usage → Detect memory pressure or leaks.
• Disk I/O → Check disk bottlenecks.
• Network I/O → See traffic spikes.
• Processes → Monitor which processes (PHP, Nginx, Postgres) use most CPU/RAM.
• PostgreSQL Section → View DB connections, cache hit ratio, lock conflicts.

🚩 Debugging Performance Issues:

1. Check CPU → If spikes to 100%, it's CPU-bound.
2. Check Disk Backlog → If backlog >0 consistently, it's disk I/O bound.
3. Check Processes → See if PHP-FPM, Postgres, or Nginx are top consumers.
4. Monitor Network → High inbound/outbound during stress tests.

📛 Stop Netdata (if needed):

sudo systemctl stop netdata

🔥 Recap:

• Netdata is installed via one-line script.
• Accessible on port 19999.
• Best practice → Use SSH tunneling for secure access.
• Monitors full system: CPU, RAM, Disk, Network, and Apps like Postgres.
• Provides real-time debugging during stress testing or production load.