-
Notifications
You must be signed in to change notification settings - Fork 1
fping Plugin
The fping plugin supports monitoring latency, packet loss and uptime of any number of hosts, by pinging them with fping.
A recent version of fping is required (one that supports option -N). The supplied plugin can install it. Run:
/usr/libexec/netdata/plugins.d/fping.plugin installThe above will download, build and install the right version as /usr/local/bin/fping.
Then you need to edit /etc/netdata/fping.conf (to edit it on your system run /etc/netdata/edit-config fping.conf) like this:
# uncomment the following line - it should already be there
fping="/usr/local/bin/fping"
# set here all the hosts you need to ping
# I suggest to use hostnames and put their IPs in /etc/hosts
hosts="host1 host2 host3"
# override the chart update frequency - the default is inherited from netdata
update_every=1
# time in milliseconds (1 sec = 1000 ms) to ping the hosts
# 200 = 5 pings per second
ping_every=200
# other fping options - these are the defaults
fping_opts="-R -b 56 -i 1 -r 0 -t 5000"The latest version of the config: https://github.com/netdata/netdata/blob/master/conf.d/fping.conf
netdata will automatically attach a few alarms for each host. Check the latest versions of the fping alarms here: https://github.com/netdata/netdata/blob/master/conf.d/health.d/fping.conf
For example, to update the chart every 10 seconds and use 2 pings every 10 seconds, use this:
# Chart Update Frequency (Time in Seconds)
update_every=10
# Time in Milliseconds (1 sec = 1000 ms) to Ping the Hosts
# The Following Example Sends 1 Ping Every 5000 ms
# Calculation Formula: ping_every = (update_every * 1000 ) / 2
ping_every=5000You may need to run multiple fping plugins with different settings for different hosts. For example, you may need to ping a few hosts 10 times per second, and others once per second.
netdata allows you to add as many fping plugins as you like.
Follow this procedure:
1. Create New fping Configuration File
Step Into Configuration Directory
cd /etc/netdataCopy Original fping Configuration File To New Configuration File
cp fping.conf fping2.confEdit fping2.conf and set the settings and the hosts you need
2. Soft Link Original fping Plugin to New Plugin File
Become root (If The Step Step Is Performed As Non-Root User)
sudo suStep Into The Plugins Directory
cd /usr/libexec/netdata/plugins.dLink fping.plugin to fping2.plugin
ln -s fping.plugin fping2.pluginThat's it. netdata will detect the new plugin and start it.
You can name the new plugin any name you like. Just make sure the plugin and the configuration file have the same name.
General
- Home
- Why netdata
- Installation
- Installation with docker
- Command Line Options
- Configuration
- Log Files
- Tracing Options
Running Netdata
Special Uses
-
netdata for IoT
lower netdata resource utilization -
high performance netdata
netdata public on the internet
Notes on memory management
-
Memory deduplication
half netdata memory requirements - netdata virtual memory size
Database Replication and Mirroring
- Replication Overview
-
monitoring ephemeral nodes
Use netdata to monitor auto-scaled cloud servers. -
netdata proxies
Streaming netdata metrics between netdata servers.
Backends
archiving netdata collected metrics to a time-series database
-
netdata-backends
graphite,opentsdb,kairosdb,influxdb,elasticsearch,blueflood - netdata with prometheus
- Walk Through: netdata with prometheus and grafana
Health monitoring - Alarms
alarms and alarm notifications in netdata
- Overview
-
Reference
reference for writing alarms -
Examples
simple how-to for writing alarms -
Notifications Configuration
- health API calls
- troubleshooting alarms
Netdata Registry
Monitoring Info
-
Monitoring web servers
The spectacles of a web server log file -
monitoring ephemeral containers
Use netdata to monitor auto-scaled containers. - monitoring systemd services
-
monitoring cgroups
Use netdata to monitor containers and virtual machines. -
monitoring IPMI
Use netdata to monitor enterprise server hardware - Monitoring disks
- Monitoring Go Applications
Netdata Badges
Data Collection
- Add more charts to netdata
- Internal Plugins
- External Plugins
-
statsd
netdata is a fully featured statsd server -
Third Party Plugins
netdata plugins distributed by third parties
Binary Modules
Python Modules
- How to write new module
- apache
- beanstalk
- bind_rndc
- ceph
- couchdb
- cpuidle
- cpufreq
- dns_query_time
- dovecot
- elasticsearch
- exim
- fail2ban
- freeradius
- go_expvar
- haproxy
- hddtemp
- httpcheck
- icecast
- ipfs
- isc_dhcpd
- litespeed
- mdstat
- megacli
- memcached
- mongodb
- mysql
- nginx
- nginx_plus
- nsd
- ntpd
- ovpn_status_log
- phpfpm
- portcheck
- postfix
- postgres
- powerdns
- puppet
- rabbitmq
- redis
- rethinkdbs
- retroshare
- sensors
- spigotmc
- springboot
- squid
- smartd_log
- tomcat
- traefik
- unbound
- varnish
- w1sensor
- web_log
Node.js Modules
BASH Modules
Active BASH Modules
Obsolete BASH Modules
- apache
- cpufreq
- cpu_apps
- exim
- hddtemp
- load_average
- mem_apps
- mysql
- nginx
- phpfpm
- postfix
- sensors
- squid
- tomcat
API Documentation
Web Dashboards
-
Learn how to create dashboards with charts from one or more netdata servers!
Running behind another web server
Package Maintainers
Donations
Blog
-
December, 2016
Linux console tools, fail to report per process CPU usage properly
-
April, 2016
You should install QoS on all your servers (Linux QoS for humans)
Monitor application bandwidth with Linux QoS (Good to do it, anyway)
Monitoring SYNPROXY (Linux TCP Anti-DDoS)
-
March, 2016
Article: Introducing netdata (the design principles of netdata)