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
51 Commits 13 Branches 14 Tags 3.7 MiB
Go 98.3%
Python 1.6%
Go to file
Julian Kornberger 5d9cee48dd Add initial delay for collectors 2016-03-12 18:26:54 +01:00
data Update comment on Statistics 2016-03-12 18:18:35 +01:00
models Copy data structs from node-informant/gluon-collector/data 2016-03-12 16:21:09 +01:00
respond Add initial delay for collectors 2016-03-12 18:26:54 +01:00
websocketserver Use direct assignment 2016-02-26 10:40:17 +01:00
.gitignore switch to config-file 2016-03-07 09:55:58 +01:00
.gitmodules switch to config-file 2016-03-07 09:52:52 +01:00
README.md Update README 2016-03-12 16:43:58 +01:00
config_example.yaml Store statistics to influxdb 2016-03-12 03:36:02 +01:00
main.go Rename -c to -config 2016-03-12 16:40:41 +01:00
stats_db.go Optimize batch insertion 2016-03-12 16:30:20 +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
  • Storing statistics in InfluxDB to be analyzed by Grafana
  • Provide information via Websocket- and JSON-APIs

Usage

Usage of ./micro-daemon:
  -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.

A Implementation of the connection to influxdb are also needed, maybe log a little bit to telegraf from influxdb.