Open Source Software Testing Tools

DBD2 inserts database records from TCP input. It is a companion project to Syslgod2 and an application in its own right. It ships with a backgrounding client for generic use. The client sends whatever information the user puts on the command-line to the back-end daemon via TCP. Upon successful transmission, the client exits. On failure, it backs off and retries until its life-time timer expires. The back-end daemon accepts data from Syslogd2 or its own client and inserts that data (and envelope information) into one or more databases using MySql client library or dbi drivers (also on SourceForge). The client needs no configuration (all input is via command-line). It is intended for hosts to make database entries without needing database client or interface code. Syslogd2 integration allows DBD2 to act as Syslogd2's database back-end for MySql and other databases supported by the dbi drivers. Original purpose was to track Linux cluster job status but other uses exist.

A distributed logging & monitoring WS architecture using WS-Notification (WSN) as well as a Log4J appender that implements an appropriate adapter. Software components that already use Log4J can be integrated non-intrusively.

Using templated message formats with customisable placeholders, run in configurable sequences that can selectively reuse data between steps, must allows more intelligent testing of syslog receivers with realistic data, as well as longer soak testing and stress testing. must was created to fill a gap found when trying to stress test Splunk as real, indexable and meaningful data was needed. must will (eventually) be provided as a standalone tool that uses XML configs (for quick use and consultancy etc) and as a web-based tool (for more permanent/pretty deployment (with historical reporting and live stats). SUPPORT: The best way of contacting me is via Twitter below, NEWS: (16/Mar/15) A beta of v2 is finally released - apologies for the long delay!