NetData is a simple, real-time systems monitoring platform that collects thousands of metrics per server quickly and effectively. If you want to know what’s happening with your server and network devices, install the NetData tool.
This brief tutorial shows students and new users how to install and configure the NetData monitoring server on Ubuntu 16.04 | 18.04 LTS servers.
NetData also analyzes thousands of metrics per server, everything about the system (CPU, RAM, disks, network, firewall, QoS, NFS, ZFS, etc.). A complete enterprise-grade network, server, and log monitoring system.
This post will show you how to perform a basic configuration after installation. You can also log on to the NetData server once installed.
For more about NetData, please visit its homepage.
When you’re ready, continue below with the steps:
NetData packages come with Ubuntu default repositories.
That makes it easy to install. No repositories to add or packages to manually download.
Just run the commands below to install NetData.
sudo apt update sudo apt install netdata
That should install NetData packages and all their dependencies. After installing, run the commands to open its configuration file and bind the server IP address.
sudo nano /etc/netdata/netdata.conf
Then change the line to bind to the server’s IP address and save the changes. By default, it will bind to the server loopback address. If you want to specify a dedicated IP, replace the one below with it.
[global]
run as user = netdata
web files owner = root
web files group = root
# Netdata is not designed to be exposed to potentially hostile
# networks.See https://github.com/firehol/netdata/issues/164
bind socket to IP = 127.0.0.1
After restarting the NetData service to apply the changes.
sudo systemctl restart netdata
After restarting the service, open your browser and browse to the server IP address or hostname followed by port 19999
http://localhost:19999
That should bring up the NetData default monitoring page with the stats page.

Alarms can be configured on any metric monitored by net data. Alarm notifications are role-based and support dynamic thresholds and hysteresis and can be dispatched via multiple methods (such as email, slack.com, pushover.net, pushbullet.com, telegram.org, and twilio.com).
That’s it!
You may also like the post below: