Export to GitHub

pomamonitor - RoadMap.wiki

Roadmap

Here you will find ideas on next features and changes on Poor's Man Monitor. They're divided in three sections: Imature ideas, Mature ideas and Already Implemented. They are listed with the following pattern:

  • Title: A short description.
  • Description: A long description
  • Blocked by: What is avoiding/blocking the feature from being developed

  • New dependecies: New software dependencies this feature will require.

  • Title:

  • Description:
  • Blocked by:
  • New dependecies:

Immature ideas are just a initial draft, without single test done so far. Mature ideas are more viable, had already some sort of testing or it is clear how it should be implemented.

How to comment these ideas?

Liked some of these ideas? Would you like to comment or request them to be implemented? Just speak out in our mailing list

Immature Ideas

  • Title: Import/Export data through CSV files
  • Description: pomamonitor may deal with a huge amount of data, monitoring hundreds of targets. Dealing with so many targets may be difficult to add or extract data from pomamonitor. So pomamonitor could storage all information it has about targets in a CSV file, allowing imports/exports of data. This would also allow other programs to include or exclude targets to be monitored by pomamonitor.
  • Blocked by: Lack of requests for this feature.

  • New dependecies: none.

  • Title: a GUI for settings.

  • Description: At the first run, there is a GUI that makes questions to the user to generate pomamonitor.conf. But later, if the user wants to change a config, like adding a target to be monitored, he will need to edit pomamonitor.conf using a text editor. A GUI could be implemented to avoid 100% the need of editting the conf file manually.
  • Blocked by: Lack of requests for this feature.

  • New dependecies: none.

  • Title: Extensive IRC monitoring

  • Description: IRC servers are quite hard to monitor. They may respond to pings, they may even have the TCP port 6667 open and responding quickly but without access to services (NickServ, ChanServ) and even not linked with the rest of a IRC network.
  • Blocked by: Lack of requests for this feature.

  • New dependecies: ii or epic5

  • Title: Dealing with large output

  • Description: If more than 5 targets are offline, notify-send won't list all of them to avoid a very big area. New ways of outputing a full list of offline hosts should be implemented.
  • Blocked by: Lack of requests for this feature.

  • New dependecies: none.

  • Title: Monitoring online hosts

  • Description: Currently, pomamonitor belives all targets must be online and will alert with a target is detected as offline. Sometimes, a user would like to detect the oposite: a target that is mostly offline or expected to be offline and he want to be alerted if this host is detected as online.
  • Blocked by: Lack of requests for this feature.

  • New dependecies: none.

  • Title: Centralized log

  • Description: pomamonitor outputs valuable data and many people would like to record them. to keep track on the uptime/downtime percentage of theirs systems. Currently, pomamonitor outputs rich data on an terminal if it is running from a terminal window. Such data should be saved in a centralized log.
  • Blocked by: Low understanding on how logrotate tool works and other methods of avoiding huge and endless logs work. Implementation ideas needed.
  • New dependecies: none.

Mature Ideas

  • Title: Show favicon.ico from a target
  • Description: If a single target is offline and it was running a webserver with a favicon.ico availuable, pomamonitor would show this icon instead of it's own icon.
  • Blocked by: Mostly favicon.ico are very low resolution images and notify-send will automatically resize then, making it look very ugly. This require an investigation on a better way of showing this image.

  • New dependecies: curl

  • Title: Port monitoring

  • Description: Currently, pomamonitor only checks if a host is online or offline if with pings (ICMP ECHO). Some targets won't respond to pings, making pomamonitor unable to monitor them and ping is not a rich data: sometimes a targets is responding to pings but a daemon had stopped working. Port monitoring would add a more precise monitoring for pomamonitor.
  • Blocked by: Lack of requests for this feature.

  • New dependecies: nmap

  • Title: Extensive HTTP monitoring

  • Description: HTTP servers are quite hard to monitor. They may respond to pings, they may even have the TCP port 80 open and responding quickly but with an error, like HTTP 500 error or a page saying that database could not be reached. An extensive HTTP monitoring would detect HTTP errors (like HTTP 500) or even find keywords in the page body that indicates something went wrong (like PHP or database errors)
  • Blocked by: Lack of requests for this feature.

  • New dependecies: curl

  • Title: Support CIDR targets

  • Description: Sometimes a system administrator wants to monitor a full block of IP addresses, like 192.168.0.0/24. pomamonitor should be able to interpret this as a valid target and monitor all 254 IP addresses that are expressed by such notation.
  • Blocked by: Lack of requests for this feature.
  • New dependecies: none.