Skip to content

Latest commit

 

History

History
30 lines (16 loc) · 1.57 KB

TODO.rdoc

File metadata and controls

30 lines (16 loc) · 1.57 KB

  • Notification scheduler should be tagged so that it could be controlled (start/stopped)

  • Follow REST completely for status updates, Add status updates delete/restart/stop by id instead by tag

  • Add validation for the REST api input data

*Ragios::Server may need to should have an exception class to allow clients like the RESTserver know exactly what a problem is with specific details.

*Ragios URL plugin should allow users to set the timeout

*Ragios URL plugin should allow users to set the type of http request they choose either a GET or POST and include body data for a POST

*Plugins should be able to override all methods of the Ragios::Monitors::System class. Making plugins firstclass Monitors

Goals for versions 0.5.2 ↑

TODO ↑

  • Add a web UI admin dashboard for using Ragios Server.

DONE ↑

*Complete test coverage of the new system

*Create a plugin architecture, so that all monitors (like HTTP, DNS,process monitors) are added as plugins. This will also allow developers to easily write customized plugins. OR easily install plugins written by other developers.

*Create a simple http server for Ragios that responds to REST requests. This will enable other apps to communicate with Ragios via REST. Example a Rails,Sinatra or javascript app could provide a Web UI for Ragios via REST. The datafeed from Ragios could be fed to webpage, blog or mobile app.

*Add ability to persist Ragios information and real-time statistics to a database. This will allow service performance monitoring overtime. It will also enable better monitor control.

*Document the new Ragios system 0.5.1