nxlog is a modular, multi-threaded, high-performance log management solution with multi-platform support. In concept, it is similar to syslog-ng or rsyslog, but is not limited to Unix/syslog only. It can collect logs from files in various formats, receive logs from the network remotely over UDP, TCP, or TLS/SSL on all supported platforms. It supports platform-specific sources such as the Windows Eventlog, Linux kernel logs, Android device logs, local syslog, etc. Writing and reading logs to/from databases is also supported for many database servers. The collected logs can be stored into files, databases, or forwarded to a remote log server using various protocols. The old BSD Syslog and the newer IETF syslog standard (RFC 3164 and RFC 5424-5426) are fully supported by nxlog in addition to XML, JSON, CSV, GELF, and other custom formats. A key concept in nxlog is to be able to handle and preserve structured logs so there is no need to convert everything to syslog and then parse these logs again at the other side. It has powerful message filtering, log rewrite, and conversion capabilities. Using a lightweight, modular, and multi-threaded architecture which can scale, nxlog can process hundreds of thousands of events per second.
Feed4JUnit makes it easy to write parameterized tests for the JUnit framework and feed them with predefined or randomly generated test data: test case data can be read from Excel or CSV files, databases, or custom data sources, and equivalence class tests can be defined easily. Setup is based on Java annotations and is easy to learn, apply, and maintain. Annotations defined in the "Bean Validation" JSR 303, Java 7, and Benerator are automatically recognized and generated smoke test data will match the constraints. By connecting to Benerator, you can configure generation of complex valid and invalid data sets.
Feed4TestNG makes it easy to write parameterized tests for the TestNG framework and feed them with predefined or randomly generated test data: test case data can be read from Excel or CSV files and equivalence class tests can be defined easily. Setup is based on Java annotations and easy to learn, apply, and maintain. Annotations defined in the "Bean Validation" JSR 303, Java 7 and Benerator are automatically recognized and generated smoke test data will match the constraints. By connecting to Benerator, you can configure generation of complex valid and invalid data sets.
DynaBlast is a fast Apache HTTPD access_log scanner. It can find hosts that exceed a given number of hits in a given time period, printing them to standard output. It has a "fast mode" that can skip lines that have already been parsed. Multiple dynablast instances are avoided by using a lock file. This make it suitable for crontab usage. It can be run by any user, not just root. It can run in parallel, for example, when analyzing different access_log files. It keeps memory consumption down to about 10 kb, by parsing the access_log file one line at a time.
Osgish is a command line shell for OSGi. It is based on the Readline Library, Jmx4Perl, as the OSGi backend, and Aries JMX as the OSGi Management layer. It is different than other OSGi shells, as it is implemented in pure Perl and provides unique features like wildcard support, context-sensitive command line completion, syntax highlighting, bulk lifecycle operations, advanced query facilities, and remoting via HTTP. It uses jmx4perl and Aries JMX OSGi bundles for accessing the OSGi container remotely.
FusionInventory Agent is an generic inventory agent that can collect information from various sources including the local machine, network, and remote devices. It also has the ability to send Wake on LAN requests and deploy software. The agent can be used with GLPI, Uranos, Rudder, Pulse2, and OCS Inventory.
OpenSVC is a 'service' manager, as in clustered service manager. Services are described as collections of resources (IP, disk groups, filesystems, file synchronizations, and application launchers). Services can be started, stopped and queried for status, providing a consistent command set for wildly different service integrations. Services can be administered using a stand-alone free software stack deployed on the nodes (nodeware). Service configurations, status, and logs are pushed to a central database coupled to a Web front-end (collector).