pdr (personal data recorder) and pdx (personal data expert) are applications that collect and evaluate mostly numeric personal data. The intended use case is for logging individual medical data (blood sugar, blood pressure, body temperature, weight, heart rate, and medications), but they can also be used for technical, sports, fitness, weather, environmental, or financial data. They work on a continuous flow of numbers in time that you want to monitor. Every data item can also be commented by text. pdr can use Twitter and email accounts for data input, which makes mobile phones usable for data input. It is one of the few free applications for diabetics.
PostRemoteLog is a tool that allows you to send information across the network to a centralized location. Three methods are currently supported: XMLRPC, Email, and Growl. It is generally aimed at system administrators who want to keep track of information such as backup post-run scripts, network monitoring scripts, UPS information, service outages, power on/off, unexpected restarts, etc. PostRemoteLog is designed to be used in other scripts. Captured data can be analyzed and aggregated as needed.
ColorLogs is an output-colorizing Perl script intended to have command output piped through it to a terminal. It allows easy creation of new highlighting configurations using simple text matches, globs, or regular expressions. It works transparently even in interactive contexts with scripts that produce prompt lines and wait for user input. Patterns are provided for Ant and Maven output. This version started as a fork of v1.1 from resentment.org, but numerous improvements have been made since then.
tadedon is a set of utilities that form a foundation for applications written with one of the many Java frameworks, such as GWT, GIN, Guice, Google App Engine, commons-configuration, and many others. It lets you specify the default configuration of your application and upgrade it automatically on each new release. It can redirect all java.util.logging to slf4j and easily configure logback. It can bind application configuration in a Guice module. It supports @PostConstruct and @PreDestroy annotations (JSR 250) in Guice applications. It lets you annotate your methods with @Transactional annotation. It supports Guice injector stage in your Web application. It lets you test your Guice managed servlets and filters without needing a real servlet container. It lets you use Guice Matchers for matching super class, interface, and type literal annotations. It can inject event bus to your GWT applications with the help of GIN.
Zbxlog provides better integration of syslog messages (as defined in RFC 3124 and 5424) with Zabbix. Currently, Zabbix cannot process messages in syslog format; it can only process messages stored in flat files by standard syslog programs on Unix/Linux systems. This means that it can't process syslog messages from devices on which Zabbix cannot be installed. It also means that several fields of a syslog message are lost (timestamp, facility, and severity). This project adds support in Zabbix for a new kind of item: "syslog[<facility>,<regexp>,<severity>,<maxlines>]". It has been tested with Zabbix 1.8.2 and 1.8.3.
liblognorm is a tool to normalize log data. It takes logs in different formats as input and outputs the data within them in a single, consistent format. For example, if you have traffic logs from three different firewalls, liblognorm will be able to normalize all the events into a generic form. Among other features, it can extract source and destination IP addresses and ports and make them available via well-defined fields. The result is that a common log analysis application will be able to work on that common set independently from the actual firewalls feeding it. Even better, once a well-understood interim format exists, it is also easy to convert that into any other vendor specific format, so that you can use that vendor's analysis tool.