Free reporting solutions software for linux

E/AS Automation Solutions is open source software system for help automate your solutions even for personal and/or corporate ones.
E/AS written on CLIP language (CA-Clipper dialect, compiler can be obtained from ITK.ru) and uses CODB (CLIP Object Database) as data storage.
Main features:
- client-server technology (both data and interface forms)
- component infrastructure with interaction between components by messages
- interface forms on XML
- MDI
E/AS contains in typical distribution:
- client software written on clip-ui library
- server software with wrapper for run as daemon
- maintenance tools: CODB console and component manager
- base (form, auth) and example (contact) components
Enhancements:
- completely rewrite code for implement E/AS architecture
- component infrastructure
- own server program instead COBRA
- maintenance tools: CODB console and component manager
- base and example components
- autoupdate views

SrvReport is a simple and featurefull server monitoring and reporting system. SrvReport project can send every day a mail with the latest state of the server including:
- network traffic report
- cpu usage report
- mail send/receive
- server warnings
- last logins
- other customized messages (like harddisk problems)
- web-server traffic report
- Xfer-logs (ftp)
- optional test for rootkits (with chkrootkit)
Main features:
A full report will show you the following information:
- Network traffic (including dayly, weekly and monthly graph)
- CPU-Usage (including dayly, weekly and monthly graph)
- Mail sent/receive report (to, from, size)
- Last authenticated users
- Server warnings
- Other customized messages (like harddisk problems)
- Optional web-server traffic report
- Optional Xfer-logs
- Optional test for rootkits (with chkrootkit)
It supports the following features as well:
- Several languages
- No need of rare perl libraries
- Easy to use (Just one configuration file to edit),
- Free (GNU GPL), with sources (perl scripts),

Agata Report is a cross-platform database reporting tool with graph generation and a query tool that allows you to get data from PostgreSQL, MySQL, SQLite, Oracle, DB2, MS-SQL, Informix, InterBase, Sybase, or Frontbase and export that data as PostScript, plain text, HTML, XML, PDF, or spreadsheet (CSV) formats through its graphical interface.

You can also define subtotals, levels and a grand total for the report, merge the data into a document, generate address labels, or even generate a complete ER-diagram from your database.

VCS Report is a free open source Java project to generate statistical reports from your VCS repository. Versions Control System (VCS) helps to manage revisions of your source files.
You can run VCS Report on Microsoft Windows and Linux. VCS Report shows various information about your project files stored in the VCS. VCS Report can be used as a plugin for IntelliJ IDEA, Borland JBuilder, Eclipse, NetBeans.
Main features:
- CVS and Subversion (SVN) support
- Customizable filters
- History table
- Statistical charts
- HTML reports
- CSV (Comma delimited) reports
Enhancements:
- new: The time of a report was added to the status line
- bugfix: Bug with "Get report" button

Data::Report provides a framework for flexible reporting.

Data::Report is a flexible, plugin-driven reporting framework. It makes it easy to define reports that can be produced in text, HTML and CSV. Textual ornaments like extra empty lines, dashed lines, and cell lines can be added in a way similar to HTML style sheets.

The Data::Report framework consists of three parts:
The plugins

Plugins implement a specific type of report. Standard plugins provided are Data::Report::Plugin::Text for textual reports, Data::Report::Plugin::Html for HTML reports, and Data::Report::Plugin::Csv for CSV (comma-separated) files.
Users can, and are encouraged, to develop their own plugins to handle different styles and types of reports.

The base class
The base class Data::Report::Base implements the functionality common to all reporters, plus a number of utility functions the plugins can use.

The factory
The actual Data::Report module is a factory that creates a reporter for a given report type by selecting the appropriate plugin and returning an instance thereof.

Snort Report is an add-on module for the Snort Intrusion Detection System. Snort Report add-on provides realtime reporting from the MySQL database generated by Snort.

It has been tested on Redhat 6.2, 7.0, 7.1, and OpenBSD 2.9.

Zerotools project contains a set of tools to aid keeping virtual disks clean (by filling binary zero to those regions which are no longer in "use"). This is done on-the-fly or manually, depending on which tool suits the needs best.

In technical terms the on-the-fly mechanism uses LD_PRELOAD to wrap the unlink library call and zerounlink-wrapper provides a symlink based mechanism to target individual programs so that they will be run using the unlink wrapper. For comparison against other tools, please see the "Other solutions" section.

Please note that zerotools dont compete with various tools that rewrite file contents with "random" data in order to make data retrieval close to impossible. Do not use zerotools for this, or claim that they are good tools for this. Theyre not. (This text was added for people who only read introductions.)

Zerotools are Linux specific, implemented using C and licensed under GNU General Public License (v2). The tools are provided without a warranty of any kind, in the understanding that software bugs do exist and bad things can happen.

Bugs and limitations

There are no known bugs. Known to me at least. Bugs will be fixed based on intelligent reporting by end users or automatically if I have extra time. My email address is at the start of each source file should you feel the need to send patches.
Thread-protection is not yet tested properly. Neither is LFS-requirement (which means that zerotools might not be able to handle files over 2 GiB size on 32-bit architectures). Building or running zerotools on older Linux systems has not been attempted (but will be done as soon as older systems are installed in test environment). User participation in testing is also appreciated.

Testing has been done on many Linux distributions running kernels (2.4 and 2.6) and with glibc versions (2.3.2 to 2.5.3, with vendor patches, so this is advisory information only). Architectures that were tested are x86, x86_64, ia_64, and ppc (32-bit). Other architecture test results are welcome.

zerounlink and zerounlink-wrapper do not work with statically linked executables. This is a limitation in the technique and there are no workarounds (known to me).
One mis-feature exists in zerounlink: when checking whether a file should be zeroed or not, zerounlink doesnt take into account sparse files. If the file is sparse, it would make sense to overwrite only the parts of file which have non-zero content.

This means that zerounlink would have to read through all of the original file and search for the non-zero content first. This would also mean that instead of only writing to the unlinked file, zerounlink would have to read it in as well. This would cause extra I/O operations. Not sure whether special sparse-file support is worth the extra effort and complexity so this feature has not been implemented.

Drop me a note if you think you need it. (The reason for having this feature is to do with how most dynamic virtual disks are implemented. They will allocate real space when any data is written to an vdisk area, even if the writes consist of only binary zeroes. Its a bit silly, but thats how most of them work. This is the same reason why filling the filesystem with a file containing only binary zeroes (with dd or other tool) is not really a good solution to clean up the vdisk.)

When reporting bugs about listings on this web page, please include the listing number and line number of the problematic bit to speed up fixes. For other web-related fixes, try to include two to three word phrase which can be grepped with. Do not send diffs against xhtml.