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
60 Commits 13 Branches 14 Tags 3.7 MiB
Go 98.3%
Python 1.6%
Go to file
Julian Kornberger 96d8be417c Fix handling of compressed data 2016-03-19 15:07:44 +01:00
data Embed Traffic directly into Statistics 2016-03-19 03:08:19 +01:00
models add mac from nodeinfo (not from neigbours) in graphbuilder 2016-03-17 11:51:45 +01:00
respond Fix handling of compressed data 2016-03-19 15:07:44 +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
README.md Rename package to respond-collector 2016-03-15 23:26:30 +01:00
config_example.yaml Update config_example.yaml (correct paths) 2016-03-14 11:03:24 +01:00
main.go Rename package to respond-collector 2016-03-15 23:26:30 +01:00
stats_db.go Rename package to respond-collector 2016-03-15 23:26:30 +01:00

README.md

Respond Collector

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.