Roadmap

The current roadmap for nodewatch

See the milestones on the issue tracker for an idea of approximate timescales. Items that have been struck through are already implemented in HEAD.

• New Role definitions
  • Administrators control network (discovery), instrumentation and publication (interfaces)
  • Interfaces publish events (to connected users)
  • Users subscribe to events
• Historical Trends
  • Publication (interfaces) to e.g., connectd/RRDTool and the like
• API improvements
  • Add support for eper network event data
  • Simplified relationship between users/accounts and event subscriptions
  • Support adding user defined (MFA) subscribers - see notes below
  • Store historical events for a (configurable) period of time
  • Allow/configure use of Eper's proxy mode
  • REST API for Polling consumers
  • Support for atom/rss feeds (?)
• UI improvements
  • Separate admin UI for managing accounts and subscriptions
  • Graphs and sparklines instead of text/grids
  • Uplift UI layout to work across varying resolutions
• Patches/Upgrades to Eper
  • Support for configuring the timeout between event capture ticks
• Misc
  • Upgrade to latest fastlog and use fastlog-parse-trans to optimise logging calls.
• Admin/Install
  • Hook in the rebar-dist-plugin to produce pre-compiled bundles
  • Finish up with admin/install scripts
  • Provide pre-configured service bundle for cloudfoundry
  • Provide pre-configured chef/puppet templates

Notes

Adding support for registering a user defined MFA allows for simple third party customisation, so events can go onto a queue, on disk, etc. This mechanism can (and probably should) also be used to support storing a historical record of events.