304 North Cardinal St.
Dorchester Center, MA 02124
With the EOL of the free tier of NewRelic’s Server monitoring service, we tried going commando for a while, meaning no server monitoring. We know bad – bad, idea.
NewRelics Server monitoring service was great but the free tier came with only 24 hours of data retention. We wanted something which would give us more flexibility, behold netdata.
Netdata claims real-time insights of more than 5000 metrics with interactive dashboards along with performance and health monitors, all this with very little or no configuration.
Let’s get started
Start off by installing the Epel repo
yum install epel-release
Install the development tools group package
yum groupinstall "Development Tools"
Now we need to install other pre-requisites:
yum install curl nodejs jq
Fetch the netdata repo
# Navigate to your home directory cd ~ # Fetch the repo git clone https://github.com/firehol/netdata.git --depth=1 # Step into the fetched repo cd netdata
It's now time to run the installer # Run the installer ./netdata-installer.sh
For reference sake, these are the locations which netdata will be using
- the daemon at /usr/sbin/netdata - config files in /etc/netdata - web files in /usr/share/netdata - plugins in /usr/libexec/netdata - cache files in /var/cache/netdata - db files in /var/lib/netdata - log files in /var/log/netdata - pid file at /var/run/netdata.pid - logrotate file at /etc/logrotate.d/netdata
To start netdata
service netdata start # To stop service netdata stop
Add netdata to startup
chkconfig netdata on
To access netdata, make sure the service is active and navigate to:
Note: You’ll need to open port 19999 if you’re running a firewall.