/infping

Parse fping output, store result in influxdb

Primary LanguageGoMIT LicenseMIT

Introduction

infping is a simple Go program to parse the output of fping and store it in InfluxDB. Based upon software by Tor Hveem.

Configuration

This program uses the Viper configuration package and can process configuration files in JSON, YAML, TOML, and others. Save your configuration file as infping.<json|yaml|toml|...> in /etc/, /usr/local/etc, or the program directory. A sample configuration file is provided in JSON format.

influx

  • host: The hostname to connect to
  • port: The TCP port number
  • user: The username, if needed
  • pass: The password, if needed
  • db: The database name to connect to – this will be created if it does not exist
  • secure: Set to true to enable HTTPS
  • measurement: Measurement name, if needed - by default "infping"
  • policy: Retention policy to use (by default uses influx's default retention) - must be created manually

fping

  • backoff: The value for the -B argument
  • retries: The value for the -r argument
  • tos: The value for the -O argument
  • summary: The value for the -Q argument – this determines how often data is collected
  • period: The value for the -p argument

hosts

  • hosts: An array of hostnames to ping

hostname

  • hostname: Manual specification of the host (tx_host) - by default gets the os hostname

Influx Storage

Data is stored in Influx with the following fields and tags:

  • min: field showing minimum ping time during the run
  • max: field showing maximum ping time during the run
  • avg: field showing average ping time during the run
  • loss: field showing packet loss during the run
  • rx_host: tag showing the target host
  • tx_host: tag showing the originating host of the ping check

Docker

There is a beta-quality Dockerfile in the root of this repo that uses multistage builds to build and create an image of infping. Running it can be as easy as:

docker run -v /local/infping.json:/config/infping.json $IMAGE

It will automatically detect the configuration in /config. For best results, assign a hostname, otherwise you'll end up with one that doesn't make much sense

We also have a docker-compose file at /docker/docker-compose.yml with a reference to run this service.

Grafana Dashboard

A sample Grafana dashboard is included, that plots all four of the collected ping statistics in something approximating the display of Smokeping. Simply create a datasource named "infping" pointing to Influx, and then import this dashboard. The hostname variable will be automatically populated with all the host names found in the database, and can be used to select different graphs.

dashboard screenshot