GSoC 2018 – Better map for nodewatcher

Hello everyone,

My name is Marin and this year through Google Summer of Code I am contributing to the nodewatcher project and with these blog posts I will keep you updated on my progress.

Nodewatcher is one of the projects of wlan slovenija open wireless network. Its main goal is the development of an open source, modular community-oriented platform used for network planning, node deployment, node monitoring and maintenance. Currently it is used to monitor more than 1600 nodes in multiple countries. I got acquainted with nodewatcher when I joined a Croatian organization called Otvorena Mreža who uses nodewatcher to monitor their nodes.

While working with nodewatcher on Otvorena Mreža there was a recurring problem of not noticing offline nodes on time, we had an alert system that would constantly get flooded if a node kept restarting and that would hide the fact that another one is offline. Nodewatcher is based around monitoring and control of nodes so the best way to monitor multiple nodes at once should be the map, because you get a fast overview of all of them and you can also focus on one of them. The current map while functional, it only shows currently active nodes and it could do so much more. With my project I intend to add features that would allow easier and more detailed overview of nodes.

Some of the features that have came up as necessary are:

  • ability to get a fullscreen map to make it more presentable and easier to inspect
  • when hovering over a node it should list a short description about it i.e. name and number of users
  • toggle buttons to enable and disable which nodes to show (online, offline, idle)
  • color representation of the current status of the node, most importantly it should be easy to spot nodes that have gone offline recently

These are just some of the functionalities that need to be implemented to the map, after that I hope to get feedback from other nodewatcher users to see if anything else should be added or changed. Currently, the next step is to analyse the current code and see if it should be completely redone or is it possible just to upgrade it.

Leave a Reply

Your email address will not be published. Required fields are marked *