ffhb/yanic
ffhb
/
yanic
mirror of https://github.com/FreifunkBremen/yanic.git
1
0
Fork 0
Code Issues Releases Wiki Activity
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
145 Commits 13 Branches 14 Tags 3.7 MiB
Go 98.3%
Python 1.6%
Go to file
Martin Geno 8c09687e86 fix bugs rrd importer -> clients are no nodes :) 2016-10-04 15:00:54 +02:00
api api aliases delete cleanup 2016-07-13 00:09:49 +02:00
data Limit utilization to 100 % 2016-07-14 17:22:26 +02:00
database fix bugs after refactoring 2016-10-04 14:54:19 +02:00
jsontime disable link for offline nodes + improve offline state 2016-06-22 09:16:06 +02:00
meshviewer update nodes 2016-06-16 18:50:43 +02:00
models Add global statistics 2016-10-04 01:06:24 +02:00
respond fix bugs after refactoring 2016-10-04 14:54:19 +02:00
rrd fix bugs rrd importer -> clients are no nodes :) 2016-10-04 15:00:54 +02:00
.gitignore airtime + no panic on lost of influxdb connection 2016-07-04 14:46:45 +02: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 multi nodes 2016-06-16 18:03:45 +02:00
main.go Use defer 2016-10-04 00:50:39 +02: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.

Related projects

Collecting data from respondd:

Respondd for servers: