Free real spy monitor software for linux

The Monitor application, which consists of 2 parts, a MonitorServer (linux daemon) and a MonitorClient (java gui), will enable the user to monitor and log server process, memory, network and cpu information of multiple servers at a time.

The MonitorClient part is written in Java and is able to connect to one or more Servers that are running the MonitorServer part of the Monitor application.

The client will poll the servers at user specified intervals and will provide a graphical representation of the recources (mem, cpu, nic and process information) of one server at a time.

In addition the MonitorClient is able to log the information of all the servers, each server in a different logfile in a coprehesive CSV format.

The MonitorServer is a seperate application written in C++ and linked to omniORB4 to minimize the load it imposes on the server that is beeing monitored. When the MonitorServer is not beeing polled by a MonitorClient it sits idle.

The client will of course run on any platform that supports Java, but the server currently only supports Linux, kernels 2.2, 2.4, 2.6 and possibly (not tested) 2.0 and >2.6.

The Linux Duracell CPU load monitor is a program that drives a Duracell or Energizer on-battery tester to display the CPU load of a system.

It can be easily adapted to display other things that can use a slow bar graph kind of display that varies between 0% and 100%.

Instructions to hack a AA-battery tester and turn it into a computer display are included in the distribution.

Aazmat Monitor is a SuperKaramba system monitoring widget.

It was adapted to meet office theme and added a few new monitors all of them are built into there own theme file so you can place them were you like.

X Hardware Monitor is a hardware monitor that shows indicators for temperature, voltage, fan speed etc, of a running system with a graphical panel.

The default configuration allows to monitor up to 3 temperatures, 3 fan speeds and 6 voltages. This tool is more particularly adequate for bi-processor systems.

The ORTE is an implementation of the RTPS communication protocol defined by Real Time Innovations.

RTPS is an application layer protocol targeted to the real-time communication area. It is built on top of a standard UDP stack.

This protocol is being submitted to the IETF as an informational RFC and has been adopted by the IDA group.

UPS monitor is a graphical monitoring application that lets users watch a your UPSs status in real time.
Main features:
- Saves your session if UPS switches to battery power
- Warns you when power is critically low
- Lets you monitor networked UPSes
- Remembers configuration and restarts when you log on
- Extremely easy to use

NAT Monitor is a tool to monitor hosts bandwidth usage in a Linux-NAT network.

A daemon collects data and clients display them (currently a GTK app with graph and a text version). It detects new hosts, saves up to 12 hours of data, and has a nice summary statistic.

Craftsman Spy is a an open source and free framework for JDBC logging. Craftsman Spy is a JDBC driver implementation.

This logger logs all SQL connection and processings with execution spent time, all the stored procedures with arguments, all the batch processings and the result sets.

No need to modify your application in order to integrate JDBC logging with Craftsman Spy. The application MUST use the craftsman.spy.SpyDriver and MUST be launched with the -Dspy.driver=... system property.

Be carefull this JDBC driver SHOULD not be used in production mode. Use it only in development or pre-production system.

,b>Usage:

Code

The two solutions can be used as the following examples :
System.setProperty("spy.driver","vendor.database.Driver");// or with the -Dspy.driver=vendor.database.Driver JVM option
Class.forName("craftsman.spy.SpyDriver");
Connection c = DriverManager.getConnection("jdbc:database:mydata");
Class.forName("craftsman.spy.SpyDriver");
Connection c = DriverManager.getConnection("jdbc:spy:vendor.database.Driver:database:mydata");

Log configuration

The log4j.properties or log4j.xml configuration file SHOULD contain the following lines :
log4j.category.craftsman.spy=DEBUG, SpyFile
log4j.appender.SpyFile=org.apache.log4j.DailyRollingFileAppender
log4j.appender.SpyFile.DatePattern=.yyyy.MM.dd
log4j.appender.SpyFile.File=spy.log
log4j.appender.SpyFile.layout=org.apache.log4j.PatternLayout
log4j.appender.SpyFile.layout.ConversionPattern=%m%n