Notes on ScopePort

This is the first post in this blog. It will inform you about the current state of ScopePort development.

Right now there is only one developer. Me. I am writing the Server itself (C++), the Linux and *BSD clients (C++), the Web Interface (PHP) and everything else related to ScopePort.

Current screenshots can be found on ScopePort.org: http://scopeport.org/see-it

Where I am right now

The following parts of ScopePort are ready to go into the next phase:

• Web Interface layout and structure
• Web Interface sections: User management, adding/deleting/updating service checks and hosts, notification groups, blacklist, service check details and overview, host overview and details, log, graphs.
• Server: Thread handling, client handling, service checks (with protocol checks), notifications in case of errors, fallback modes in case of failed database server, check for “dead” clients that stopped sending sensor data,
• Client: Sensors, profile sensors,

What needs to be done to reach a feature freeze?

• Web Interface install tool
• New features: “Global severity level”,  “public status” page and “user defined screens”
• General improvements in usability of the web interface
• More features that help you managing your servers. (Like the already completed features “Todo list” and “Detailed descriptions” that are available for every host)
• Packaging and correct GNU/Autotools usage for the server and client packages.
• remote.php API of the Web Interface that will be used by the ScopePort Console nCurses (which has no release plan yet)

What needs to be done to reach a public beta?

• Documentation
• Stability testing (especially checks for memory leaks)
• Security testing
• Testing of web interface in different browsers
• Checking for XHTML validity of web interface

Contact me if you are interested in joining development, beta testing or if you have questions.