Free data collector software for linux

It is a package useful to collect statistics from remote nodes. That includes standard server metrics and any other numerical quantity we can use to characterize the node state (as the number of users or processes).

It is built under a distributed agent-manager model. RRDtool is used as database, so representation capabilities are bundled.

Although rrdUtils are not a requisite, they are used in some auxiliar tasks and using both tools is highly recommended.

Installation:

Manager side

gunzip -c rrdUtils-3.1.tar.gz | tar -xf -
cd rrdUtils
./configure --with-rrddir=/stats
make install

gunzip -c stats-station-3.0.tar.gz | tar -xf -
cd stats-station
./configure --with-statsdir=/stats --with-port=666
make install

cd rrdConf
./install_confs.sh
./haz_index.sh -g

The -g flag creates graphs with the html pages, and reduces the number of error messages that haz_index will issue.
The only task that needs to be completed at this point is the periodic graphs generation by a crontab entry that calls the make_graphs.sh script.
Once we start the server using the provided initscript, we get the manager side ready.

Agent side

gunzip -c stats-3.0.tar.gz | tar -xf -
cd stats
./configure --with-host=central.node --with-port=666
--with-statsdir=/usr/local/stats
make install

With a crontab entry to execute the statlaunch script every 15 minutes, the whole system is up and running.

libGarbageCollector is an incremental garbage collector with a tri-color, Baker treadmill, write-barrier implementation.

libGarbageCollector is built from the garbage collector code used in the Io programming language project.

Data.FormValidators aim is to bring all the benefits of the perl module Data::FormValidator over to javascript, using the same input profiles (they can be dumped into javascript objects using the perl module Data::JavaScript.
Data.FormValidator library lets you define profiles which declare the required and optional fields and any constraints they might have.
The results are provided as an object which makes it easy to handle missing and invalid results, return error messages about which constraints failed, or process the resulting valid data.
IMPORTANT NOTE: JavaScript form validation is NOT a replacement for data validation in your backend scripts. This is the primary reason this module was written... so that it would be easy to share the same validation profile for both the frontend (via Data.FormValidator.js) and backend (via Data::FormValidator.pm).
Enhancements:
- A problem where some functions were not terminated by a semi-colon, so JavaScript compactors would end up creating broken code was fixed.

System Configuration Collector in short SCC, collects configuration data of systems in snapshots. The structure of the snapshot allows SCC to compare a snapshot with the previous one and detect changes in the configuration.
Upon detecting changes, scc adds the differences to a logbook. The snapshot and the logbook are converted to HTML for local inspection. Optionally, the SCC-files can be send to a system running the SCC server software. On the server, summaries of the SCC-data are generated and search/compare operations on the snapshots and logbooks are available via a web-interface.
The logbook is a starting point in case a system "suddenly" does not work correctly and the administrator is wondering what he/she has changed in the last weeks or months. As most of us know by experience, configuration changes can have accidental side-effects on (other) systems.
By examining the entries in the logbooks and considering the consequences, the cause of an actual problem might be found more easily than by just trying to remember the changes that were performed.
The snapshots can be used to compare the configuration of two systems. Imagine systems, that are supposed to be identical, but behave differently. Comparing parts of the snapshots of the two systems can indicate the cause of the difference in behavior.
Enhancements:
- The DIV tags in the HTML was corrected.
- Directory data/transfer was created to avoid errors in scc-pull. cpu-speed for SunOS was added.
- The machinfo variable is now initialized.
- The determination of local filesystems on Linux was corrected.
- Squid classification was corrected.

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.

The Virtual Data Center (VDC) is a digital library system "in a box" for numeric data.

The VDC is a web application which provides everything necessary to maintain and disseminate collections of research studies: including facilities for the storage, archiving, cataloging, translation, and dissemination of each collection.

It includes on-line analysis, powered by the R Statistical environment. It also provides extensive support for distributed and federated collections including: location-independent naming of objects, distributed authentication and access control, federated metadata harvesting, remote repository caching, and distributed virtual

Sunrise Data Dictionary is a library for hashtable storage of arbitrary data objects with built-in reference counting and guaranteed order iteration for the C programming language.
Sunrise Data Dictionary library can participate in external reference counting systems or use its own built-in reference counting. It comes with a variety of hash functions and allows the use of runtime supplied hash functions via callback mechanism. The source code is well documented.
The Sunrise Data Dictionary was specifically designed for use within the Afelio and Callweaver telephony servers, the implementation focuses on performance and scalability.
Enhancements:
- This is the initial release of the full API (all header files) and a developer snapshot of the implementation.

Data::ICal::Entry::Event is a Perl module that represents an event in an iCalendar file.

SYNOPSIS

my $vevent = Data::ICal::Entry::Event->new();
$vevent->add_properties(
summary => "my party",
description => "Ill cry if I want to",
# Dat*e*::ICal is not a typo here
dtstart => Date::ICal->new( epoch => time )->ical,
);

$calendar->add_entry($vevent);

$vevent->add_entry($alarm);

A Data::ICal::Entry::Event object represents a single event in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.