Yet another node info collector - for respondd to be used with meshviewer to Grafana (with influxdb or graphite) https://www.gitbook.com/book/freifunkbremen/yanic/details
Go to file
Julian Kornberger 00da215efc Add related projects 2016-03-21 22:53:45 +01:00
data Request all data types at once 2016-03-19 23:27:02 +01:00
jsontime Fix jsontime and extend tests 2016-03-21 10:56:07 +01:00
models Add test for nodes.Update() 2016-03-21 12:26:08 +01:00
respond Deflate directly 2016-03-19 23:34:40 +01:00
websocketserver Use direct assignment 2016-02-26 10:40:17 +01:00
.gitignore Rename package to respond-collector 2016-03-15 23:26:30 +01:00
.gitmodules switch to config-file 2016-03-07 09:52:52 +01:00
.test-coverage Add Coveralls 2016-03-20 13:51:54 +01:00
.travis.yml Add Coveralls 2016-03-20 13:51:54 +01:00
README.md Add related projects 2016-03-21 22:53:45 +01:00
config_example.yml Add test for reading the config.yml 2016-03-20 19:57:49 +01:00
main.go Add test for reading the config.yml 2016-03-20 19:57:49 +01:00
stats_db.go Rename package to respond-collector 2016-03-15 23:26:30 +01:00

README.md

Respond Collector

Build Status Coverage Status

respond-collector is a respond client that fetches, stores and publishes information about a Freifunk network. The goals:

  • Generating JSON for MeshViewer (Works with branch JSONv2)
  • Storing statistics in InfluxDB to be analyzed by Grafana
  • Provide information via Websocket- and JSON-APIs

Usage

Usage of ./respond-collector:
  -config path/to/config.yml

Development

respond

It send the gluon-neighbour-info request and collect them together.

It will send UDP packetes by the multicast group ff02:0:0:0:0:0:2:1001 and port 1001.

modes.Nodes

It cached the Informations of the Nodes and will save them periodical to a JSON file. The current nodes are saved default under nodes.json.

websocketserver

One Instance is running under /nodes which send updates or new Nodes, which are collected by respond.

Issues

Later there should be also /aliases Websocket with Authentification to manage the aliases.json with the request for changes.

Collecting data from respondd:

Respondd for servers: