Netdata

Card Puncher Data Processing

About

Netadata is a monitoring platform

This article shows you how to install it on your node

Installation

Install User

We suggest to install it as root, or certain data collectors will not be able to work. Netdata drops root privileges when running. So, if you plan to keep it, install it as root to get the full functionality.

From the install script The service user onder which the netdata service will run, has

  • its name extracted from the config file at the address Global > Run as User (Default to Netdata)
  • its group will be the first one of the found user (otherwise, it takes the name of the netdata user)

The owners of the web files (as defined here) is:

  • The Web User is extracted from the config file at the address web > web files owner (Default to Netdata running user)
  • The web group is the service user group (Default to netdata)

Directories

Extracted from the netdata-installer.sh L25

  • the daemon at NETDATA_PREFIX/usr/sbin/netdata
  • config files in NETDATA_PREFIX/etc/netdata
  • web files in NETDATA_PREFIX/usr/share/netdata
  • plugins in NETDATA_PREFIX/usr/libexec/netdata
  • cache files in NETDATA_PREFIX/var/cache/netdata
  • db files in NETDATA_PREFIX/var/lib/netdata
  • log files in NETDATA_PREFIX/var/log/netdata
  • pid file at NETDATA_PREFIX/var/run/netdata.pid
  • logrotate file at /etc/logrotate.d/netdata

where NETDATA_PREFIX default to null but can be given to the installer via the install option

netdata-installer.sh --install /opt

Port

Netdata runs on port 19999

http://your-server-ip:19999/netdata.conf

History

The history parameter controls the amount of history data kept.

For one chart ?

  • 3600 seconds (1 hour of chart data retention) uses 15 MB of RAM
  • 7200 seconds (2 hours of chart data retention) uses 30 MB of RAM
  • 14400 seconds (4 hours of chart data retention) uses 60 MB of RAM
  • 28800 seconds (8 hours of chart data retention) uses 120 MB of RAM
  • 43200 seconds (12 hours of chart data retention) uses 180 MB of RAM
  • 86400 seconds (24 hours of chart data retention) uses 360 MB of RAM

Status

systemctl status netdata
● netdata.service - Real time performance monitoring
   Loaded: loaded (/etc/systemd/system/netdata.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2019-12-31 21:48:15 CET; 30s ago
 Main PID: 6817 (netdata)
   CGroup: /system.slice/netdata.service
           ├─6817 /opt/netdata/usr/sbin/netdata -D
           ├─6850 bash /opt/netdata/usr/libexec/netdata/plugins.d/tc-qos-helper.sh 1
           ├─6853 /opt/netdata/usr/libexec/netdata/plugins.d/go.d.plugin 1
           └─6859 /opt/netdata/usr/libexec/netdata/plugins.d/apps.plugin 1

Dec 31 21:48:15 vps748761.ovh.net systemd[1]: Started Real time performance monitoring.
Dec 31 21:48:15 vps748761.ovh.net netdata[6817]: SIGNAL: Not enabling reaper
Dec 31 21:48:15 vps748761.ovh.net netdata[6817]: 2019-12-31 21:48:15: netdata INFO  : MAIN : SIGNAL: Not enabling reaper
Dec 31 21:48:19 vps748761.ovh.net postfix/postqueue[7101]: fatal: Queue report unavailable - mail system is down





Discover More
Scale Counter Graph
Counter - Collector

Metrics collector query and collects metrics in order to be able to send them to a metrics server Log Collector In a instrumented application, reporter are a client piece of code which: process...



Share this page:
Follow us:
Task Runner