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
38f32952c2
Expire nodes after n days of inactivity (Ist okay so -> gleich mal ein Test auf meiner Maschine ...) |
||
---|---|---|
api | ||
data | ||
database | ||
jsontime | ||
meshviewer | ||
models | ||
respond | ||
rrd | ||
.gitignore | ||
.gitmodules | ||
.test-coverage | ||
.travis.yml | ||
README.md | ||
config_example.yml | ||
main.go |
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.
Related projects
Collecting data from respondd:
- Node informant written in Go
- HopGlass Server written in Node.js
Respondd for servers:
- respondd branch of ffnord-alfred-announce from FreiFunkNord
- respondd from Sunz3r
- respondd from Freifunk Bremen (just a proof of concept)