How to Install Netdata for Real-Time Linux VPS Monitoring
Netdata is an open-source monitoring platform that provides real-time visibility into Linux server performance. It collects system metrics and presents them through an interactive dashboard, helping administrators identify resource bottlenecks, investigate performance issues, and monitor server health.
With Netdata, you can monitor CPU utilization, memory consumption, disk activity, network traffic, running processes, and supported applications without manually executing multiple Linux commands.
In this guide, you will learn how to install Netdata on a Linux VPS, access its monitoring dashboard, configure secure access using Nginx and HTTPS, review alerts, and troubleshoot common problems.
This tutorial applies to Ubuntu, Debian, AlmaLinux, Rocky Linux, and other supported Linux distributions.
Prerequisites
- A Linux VPS with root or sudo access.
- SSH access to your server.
- An active internet connection for downloading installation packages.
- A supported Linux distribution.
- Optional: A domain or subdomain pointing to your VPS for HTTPS access.
- Optional: Nginx for configuring a secure reverse proxy.
Need a Linux server? Explore Owned Networks KVM VPS hosting for full root access and flexible server resources.
1. What Is Netdata?
Netdata is designed to collect and visualize system performance metrics with minimal manual configuration.
Its monitoring capabilities include:
- CPU monitoring: Track processor utilization, load averages, and CPU activity.
- Memory monitoring: Monitor RAM, swap, and memory pressure.
- Disk monitoring: Analyze disk throughput, utilization, and I/O latency.
- Network monitoring: Track incoming and outgoing traffic.
- Process monitoring: Identify applications consuming system resources.
- Application monitoring: Collect metrics from supported services and applications.
- Health alerts: Detect abnormal conditions using configured alert rules.
Netdata is particularly useful for VPS administrators who need immediate visibility into resource consumption and application performance.
2. Update Your Linux VPS
Before installing monitoring software, update your operating system packages.
On Ubuntu or Debian:
sudo apt update
sudo apt upgrade -y
On AlmaLinux or Rocky Linux:
sudo dnf upgrade -y
Production recommendation: Review pending updates before applying them to critical servers. Kernel updates and certain package upgrades may require a maintenance window or reboot.
3. Install Netdata Using the Official Installer
Netdata provides an official installation script called kickstart.sh.
Install the required download utility if necessary.
On Ubuntu or Debian:
sudo apt install -y curl ca-certificates
On AlmaLinux or Rocky Linux:
sudo dnf install -y curl ca-certificates
Download the installer:
curl -fsSL \
https://get.netdata.cloud/kickstart.sh \
-o /tmp/netdata-kickstart.sh
Review the downloaded script before executing it:
less /tmp/netdata-kickstart.sh
Run the installer:
sudo sh /tmp/netdata-kickstart.sh
Follow the installation prompts.
The installer detects the operating system and selects an installation method appropriate for the supported environment.
Security note: Download installation scripts only from trusted sources. Review scripts before executing them with administrative privileges.
Netdata installation options and package availability can change between releases. Consult the official Netdata documentation if the installer reports an unsupported platform or installation method.
4. Verify the Netdata Installation
After installation, check the Netdata service:
sudo systemctl status netdata --no-pager
If the service is not running, start it:
sudo systemctl start netdata
Enable Netdata at system startup:
sudo systemctl enable netdata
Verify that Netdata is listening on its configured port:
sudo ss -tlnp | grep 19999
Port 19999 is commonly used by the Netdata web interface.
Test the local API:
curl -fsS http://127.0.0.1:19999/api/v1/info
If Netdata is running and its local API is available, the command should return JSON information about the monitoring agent.
5. Understand Netdata Dashboard Access
Netdata commonly serves its local dashboard on TCP port 19999.
For example:
http://127.0.0.1:19999
Some installation methods or Netdata releases may provide different dashboard experiences or optional integration with Netdata Cloud.
Important: Avoid exposing port 19999 directly to the public internet. Monitoring dashboards can reveal sensitive operational information about your VPS.
For secure access, use one of the following methods:
- SSH tunneling.
- A private VPN.
- An authenticated HTTPS reverse proxy.
- A supported Netdata Cloud deployment with appropriate access controls.
6. Secure Netdata by Binding It to Localhost
For a VPS accessed through an SSH tunnel or local reverse proxy, Netdata should generally listen only on the loopback interface.
The main configuration file is commonly located at:
/etc/netdata/netdata.conf
Some installations provide a Netdata configuration editor or a configuration generation utility.
Check the installed configuration:
sudo ls -l /etc/netdata/
Back up the existing configuration before modifying it:
sudo cp -a /etc/netdata/netdata.conf \
/etc/netdata/netdata.conf.backup
If the configuration file is not present, consult the installed Netdata package's configuration instructions before proceeding.
Open the configuration file:
sudo nano /etc/netdata/netdata.conf
Under the [web] section, configure:
[web]
bind to = 127.0.0.1
If a [web] section already exists, modify its existing settings rather than creating duplicate sections.
Restart Netdata:
sudo systemctl restart netdata
Verify the listening address:
sudo ss -tlnp | grep 19999
The service should listen on 127.0.0.1:19999 rather than a public network interface.
Important: Some Netdata features, streaming configurations, or cloud integrations may require additional networking considerations. Review your deployment requirements before changing existing listener settings.
7. Access Netdata Securely Using an SSH Tunnel
SSH tunneling is one of the simplest ways to access Netdata without exposing its dashboard publicly.
From your local computer, run:
ssh -L 19999:127.0.0.1:19999 \
ubuntu@YOUR_SERVER_IP
Replace ubuntu with your SSH username and YOUR_SERVER_IP with your VPS address.
If SSH uses a custom port:
ssh -p 2222 \
-L 19999:127.0.0.1:19999 \
ubuntu@YOUR_SERVER_IP
Keep the SSH session open.
On your local computer, open:
http://127.0.0.1:19999
The connection is forwarded securely through SSH to the Netdata service running on your VPS.
This approach is particularly useful for administrators who do not need a publicly accessible monitoring dashboard.
8. Install Nginx for a Secure Reverse Proxy
If you need browser-based access through a domain name, Nginx can provide a reverse proxy in front of Netdata.
For Ubuntu or Debian:
sudo apt install -y nginx
For AlmaLinux or Rocky Linux:
sudo dnf install -y nginx
Enable and start Nginx:
sudo systemctl enable --now nginx
Before proceeding, configure a DNS record such as:
monitor.example.com
Point the hostname to your VPS public IP address.
Replace monitor.example.com with your actual monitoring hostname throughout this guide.
9. Configure Nginx Authentication
HTTP Basic Authentication can restrict access to the monitoring dashboard.
On Ubuntu or Debian, install the password utility:
sudo apt install -y apache2-utils
On AlmaLinux or Rocky Linux:
sudo dnf install -y httpd-tools
Create a password file:
sudo htpasswd -c /etc/nginx/.netdata-htpasswd monitoradmin
Enter a strong password when prompted.
Protect the password file:
sudo chown root:root /etc/nginx/.netdata-htpasswd
sudo chmod 644 /etc/nginx/.netdata-htpasswd
The password file contains password hashes, not plaintext passwords. Nevertheless, it should be protected against unnecessary disclosure.
On systems with SELinux enabled, additional file context configuration may be required for Nginx to read authentication files.
10. Configure the Netdata Nginx Reverse Proxy
On Ubuntu or Debian, create a dedicated Nginx configuration:
sudo nano /etc/nginx/sites-available/netdata
Add:
server {
listen 80;
server_name monitor.example.com;
auth_basic "Netdata Monitoring";
auth_basic_user_file /etc/nginx/.netdata-htpasswd;
location / {
proxy_pass http://127.0.0.1:19999;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 60s;
}
}
Enable the configuration:
sudo ln -s \
/etc/nginx/sites-available/netdata \
/etc/nginx/sites-enabled/netdata
On AlmaLinux or Rocky Linux, place the server block in a suitable file under:
/etc/nginx/conf.d/
For example:
/etc/nginx/conf.d/netdata.conf
Do not use the Ubuntu-specific sites-enabled symlink procedure unless your Nginx configuration supports that directory.
Validate Nginx:
sudo nginx -t
Reload Nginx:
sudo systemctl reload nginx
Security warning: This initial HTTP configuration is intended only for completing the HTTPS setup. Do not enter monitoring credentials over an unencrypted public HTTP connection.
Before enabling public access, restrict the monitoring hostname using a firewall, VPN, or trusted source IP address.
11. Enable HTTPS with Let's Encrypt
HTTPS encrypts communication between your browser and the monitoring dashboard.
On Ubuntu or Debian, install Certbot and its Nginx plugin:
sudo apt install -y certbot python3-certbot-nginx
On AlmaLinux or Rocky Linux, package availability depends on the enabled repositories.
Install Certbot and its Nginx plugin using your distribution's supported packages or the official Certbot installation instructions.
Ensure the monitoring hostname resolves to your VPS and that the required certificate validation method is available.
Request a certificate:
sudo certbot --nginx \
-d monitor.example.com
Follow the prompts to complete certificate issuance and configure HTTPS.
After HTTPS is enabled, access:
https://monitor.example.com
Your browser should request the configured monitoring username and password.
Important: For sensitive monitoring systems, HTTPS and Basic Authentication should be combined with network restrictions, VPN access, or stronger identity controls.
12. Verify HTTPS and Authentication
Check the Nginx configuration:
sudo nginx -t
Check certificate renewal configuration:
sudo certbot renew --dry-run
Verify that unauthenticated access is rejected:
curl -I https://monitor.example.com
For a protected endpoint, an unauthenticated request should normally return:
HTTP/1.1 401 Unauthorized
Depending on the HTTP version and server configuration, the response status line may differ.
Verify that direct public access to port 19999 is unavailable.
From an external system, test connectivity to the VPS public IP on port 19999.
Do not rely solely on an application login prompt to secure a monitoring service. Restrict network exposure wherever possible.
13. Monitor CPU and System Load
Open the Netdata dashboard and locate the CPU and system load charts.
Depending on the installed Netdata version and dashboard interface, available metrics may include:
- Overall CPU utilization.
- Per-core CPU activity.
- System load averages.
- CPU usage by applications.
- CPU steal time in virtualized environments.
On a VPS, sustained high CPU steal time may indicate that the virtual machine is waiting for CPU resources from the underlying hypervisor.
Short CPU spikes are common. Investigate sustained utilization that coincides with application latency or reduced responsiveness.
14. Monitor RAM and Swap Usage
Netdata provides memory charts that can help identify memory pressure and excessive swapping.
Monitor:
- Available RAM.
- Memory used by applications.
- Filesystem cache.
- Swap usage.
- Swap activity.
Low free memory does not automatically indicate a problem because Linux uses available RAM for caching.
Pay particular attention to available memory, sustained swap activity, and application performance.
Repeated memory exhaustion may indicate an application configuration issue, memory leak, or insufficient VPS RAM.
15. Monitor Disk Usage and Disk I/O
Disk monitoring helps identify storage capacity problems and I/O bottlenecks.
Depending on available collectors, Netdata can display:
- Filesystem capacity and utilization.
- Disk read and write throughput.
- Disk I/O operations.
- I/O latency.
- Device utilization.
High disk I/O latency can affect databases, websites, and application response times.
Monitor trends rather than relying on a single metric.
For additional command-line troubleshooting, use:
df -h
df -i
iostat -xz 1 5
The iostat command requires the sysstat package.
16. Monitor Network Traffic
Netdata can collect network interface statistics and visualize incoming and outgoing traffic.
Useful metrics include:
- Network receive throughput.
- Network transmit throughput.
- Packet errors.
- Dropped packets.
- Network interface activity.
These metrics can help investigate unexpected traffic spikes, connectivity issues, and application performance problems.
For additional diagnostics:
ip -s link
sudo ss -tulnp
17. Monitor Applications and Services
Netdata supports monitoring integrations for many common applications and services.
Depending on the installed collectors and application configuration, examples may include:
- Nginx.
- Apache HTTP Server.
- MariaDB and MySQL.
- PostgreSQL.
- Redis.
- Docker and container workloads.
- Systemd services.
Some integrations require additional configuration, credentials, or application endpoints.
Review the available collectors and configure only the integrations required for your VPS workload.
Security recommendation: Use dedicated monitoring accounts with read-only permissions wherever supported.
18. Configure Netdata Health Alerts
Netdata includes a health monitoring system capable of evaluating metrics against configured conditions.
Depending on the installed version and deployment method, alerts may be managed through local health configuration files or supported cloud integrations.
Common alert scenarios include:
- High CPU utilization.
- Low available memory.
- Filesystem capacity approaching critical levels.
- Disk I/O problems.
- Network interface errors.
- Application or service failures.
Review the active health configuration and notification integrations before relying on alerts for production operations.
Important: An alert visible in a dashboard does not necessarily mean that email or external notifications have been configured.
For critical infrastructure, configure an external notification channel and test alert delivery.
19. Check Netdata Resource Consumption
Monitoring software consumes some system resources.
On smaller VPS plans, review Netdata's CPU and memory consumption after installation.
Check the service:
sudo systemctl status netdata --no-pager
Inspect its processes:
ps aux | grep '[n]etdata'
Use top or htop to observe CPU and memory usage over time.
Resource consumption depends on enabled collectors, metric collection frequency, historical retention, and monitored applications.
If Netdata uses excessive resources, review its configuration and disable unnecessary collectors before changing global collection settings.
20. Troubleshooting Common Netdata Problems
Netdata service is not running: Check the service status and recent logs.
sudo systemctl status netdata --no-pager
sudo journalctl -u netdata -n 100 --no-pager
Dashboard is inaccessible: Verify that Netdata is listening on the expected address and port.
sudo ss -tlnp | grep 19999
curl -I http://127.0.0.1:19999
Nginx returns 502 Bad Gateway: Confirm that Netdata is running and that the reverse proxy points to the correct local address.
sudo nginx -t
sudo systemctl status netdata --no-pager
curl -I http://127.0.0.1:19999
HTTPS certificate problems: Verify DNS records, certificate configuration, and renewal status.
sudo certbot certificates
sudo certbot renew --dry-run
Metrics are missing: Check whether the corresponding collector is enabled and whether its required permissions or credentials are configured.
High monitoring overhead: Review enabled collectors, monitoring frequency, and historical retention settings.
21. Netdata Security Best Practices
- Keep Netdata and the operating system updated.
- Bind the monitoring service to localhost when possible.
- Use SSH tunneling or private VPN access for administrative monitoring.
- Protect browser-based access with HTTPS and authentication.
- Restrict access to trusted networks or IP addresses.
- Do not expose port 19999 directly to the public internet.
- Use least-privilege credentials for application monitoring integrations.
- Review enabled collectors and unnecessary services.
- Configure and test critical alert notifications.
- Monitor the monitoring agent's own resource consumption.
For production environments, monitoring should be combined with regular backups, firewall restrictions, secure SSH authentication, and system updates.
Related Linux VPS Tutorials
- How to Monitor CPU, RAM, Disk, and Network Usage on a Linux VPS
- How to Set Up Automatic Backups on an Ubuntu VPS Using Restic
- How to Configure UFW Firewall on an Ubuntu VPS
- How to Install and Configure Fail2ban on an Ubuntu VPS
- How to Install and Configure Nginx on an Ubuntu VPS
- How to Set Up SSH Key Authentication on an Ubuntu VPS
Monitor Your VPS with Owned Networks
Deploy websites, databases, Docker containers, and business applications on an Owned Networks KVM VPS with full root access and flexible server resources.
With real-time monitoring tools such as Netdata, you can identify performance bottlenecks, track infrastructure health, and make informed decisions about server optimization and capacity planning.
Explore Owned Networks VPS Hosting and deploy your next Linux server today.