Free reporting tool software for linux

RepTool is a reporting/printing tool.

RepTool is composed by two components: libreptool, which manages source files that are the reports definition, and it produces the report/print; greptool, which visually creates reports definition files.

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),

Tiny Report is a free software that helps you to Design, Manage, and Deliver Reports for Extreme Business Insight.
It simply automates to production of dynamic PDFs. It allows you to design your templates in OpenOffice.
Main features:
The process
- Design your .SXW fie in OpenOffice,
- Use tiny_sxw2rml.py to convert the file in a .RML template,
- Use tiny_report.py to produce PDF file using any database.
Report Designer
- The report designer used is OpenOffice. All styles, tags and features of OpenOffice documents (.SXW) are implemented instead frames.
- No specific language to learn,
- Support style, colors, table, section, items, images, ...
- OpenOffice is not needed to render the PDF
Data Acquisition
- Support python expressions for effective computation,
- Browse through table with the object relationnal mapping,
- You do not have to code the database structure (introspection on the DB),
- You can create your own object and functions
- Lots of databases supported: MySQL, Postgres, SQLite, Firebird, SybaseConnection, MAX DB
- Support all links between tables (one2many, many2one, ...),
- Lots of special features using simple Python: group, sort.
Report Renderer
- Fast, simple and easy,
- Standalone to be included in other applications.

Plone Click Tracking Tool is a product which aimed for assisting in tracking advertisement campaigns in Plone websites.

Plone Click Tracking Tool (qClickTrackingTool ) is aimed for assisting in tracking advertisement campaigns in Plone websites. It allows to track clicks of visitors. Actual statistics calculation is performed by external AWstats log analysis system.

Each campaign is assigned id and destination URL. Tool is redirecting urls of the form "portal_url/track/campaignId" to actual campaign destination.

External log analysis tool is grouping tracking log entries and provides results as a part of statistical report.

Installation includes AWstats configuration details.

The gettext lint tools is a collection of tools for checking the validity, consistency and spelling of PO and POT files. The project also includes an experimental glossary building tool.
Main features:
- POFileStatus - validator and status reporting
- POFileChecker - searches for common mistakes in PO/POT files
- POFileConsistency - consistency checker
- POFileEquiv - glossary generator
- POFileSpell - spell checker
- POFileFill - fill a file with entries already translated in other files
All the commands produce XML output; you can feed this output to report.xsl (probably located on /usr/share/gettext-lint/report.xsl) to generate HTML reports. For example:
POFileChecker $(find /path/to/po/files -name "*.po") | xsltproc /usr/share/gettext-lint/report.xsl - > report.html
The included XSL can receive the parameter css with the name of a stylesheet
to reference in the resulting HTML. For example:
POFileChecker $(find /path/to/po/files -name "*.po") | xsltproc -param css "/usr/share/gettext-lint/report.css" /usr/share/gettext-lint/report.xsl - > report.html
You can also run POFileSpell and POFileConsistency in interactive mode,
following a series of prompts. The -i option chooses this mode.
Installation
The `configure shell script attempts to guess correct values for various ystem-dependent variables used during compilation. It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions. Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release. If you are using the cache, and at some point `config.cache contains results you dont want to keep, you
may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is
also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- add POFileGlossary, a tool to check a translation against an existing glossary.
- add POFileClean, a tool to eliminate translations that are not translated.
- corrected several bugs in several tools, mainly POFileEquiv.

Directory Analysis Tool is used to analyze LDAP directories and report on their contents.

Useful if you want to find inactive accounts, people who havent changed passwords, or who has administrator privileges.

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.

Kexi Report Part is a reporting component for Kexi 1.6 based on OpenRPT 1.2.
Main features:
- A report viewer for Kexi
- An external report designer (KexiReportWriter) based on the OpenRPT writer program
Known Working Features
- Page Header
- Page Footer
- Report Header
- Report Footer
- Detail section
- Labels
- Lines
- Fields
- Page Browser
How To Create Report
1. Install the component following the instructions in INSTALL
2. Run KexiReportWriter to start designing a report
3. Select Database->Connect to DB
4. Browse to an existing Kexi Database and open it
5. Create a new report (File->New)
6. Assign a data source to the report (Document->Properties)
7. Create the report using labels/fields/lines
8. Assign columns to the field objects (Double click for properties)
9. Save the report. (Database->Save to DB)
10. Load the database in Kexi and double click the report to view it
Enhancements:
- Removed requirement to have kexi source available to install the plugin.Done this by including the needed kexi headers in the package. Only downside is that kexi 1.1.3 (from koffice 1.6.3) is required.