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
Martin Geno 16473e25cf add README 2016-02-26 09:28:31 +01:00
models fix bug 2016-02-25 21:24:54 +01:00
respond add README 2016-02-26 09:28:31 +01:00
webroot@9b507d2ea2 update webroot 2016-02-20 01:29:11 +01:00
websocketserver try close disconnected ws #1 2016-02-25 23:30:17 +01:00
.gitignore update webroot and multicast 2016-02-19 13:47:05 +01:00
.gitmodules update webroot and multicast 2016-02-19 13:47:05 +01:00
README.md add README 2016-02-26 09:28:31 +01:00
main.go add README 2016-02-26 09:28:31 +01:00

README.md

README

micro-daemon is a respond daemon to fetch information for Freifunk Nodes and represent this information with Websocket- and JSON-APIs.

Issues/Features in the Future

It will also APIs for manipulate the fetched data and give a access for ansible to push changes to the nodes.

Also it's will push statistic informations to a influxdb.

Usage

Usage of ./micro-daemon:
  -aliases string
    	path aliases.json file (default "webroot/aliases.json")
  -collectInterval int
    	interval for data collections (default 15)
  -h string
    	path aliases.json file
  -output string
    	path nodes.json file (default "webroot/nodes.json")
  -p string
    	path aliases.json file (default "8080")
  -saveInterval int
    	interval for data saving (default 60)

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.