Free monitoring software for linux

FTP Monitor is a simple panel applet, which monitors incoming connections to ftpd(vsftpd/ncftpd/pure-ftpd/proftpd) and generates passive popups.
For pure-ftpd, ncftpd, proftpd it acts as a frontend to pure-ftpwho, ncftpd_spy and ftpwho respectively. For vsftpd, it looks in output of ps -fe.
Enhancements:
- Update the change in ftp daemon (or path) withour requiring a restart
- Fixed the bug (introduced in 0.70) that FTP status will not update
- For large panels, the icon is now centered

FreeBSD ports monitoring project is a simple solution for monitoring what has changed in installed ports on a FreeBSD machine. It works quite well and shows me what is happening on some machines which are manage not only by me. And leaves some trace after handy portupgrade -a command.

But when many ports are upgraded at once output from this script becomes mess and it is hard to read what was added/removed and upgraded. Well it happens when change relates to two ports, neighbours in alphabetical sequence. Diff output with my modifiers becomes unacceptable. So I rewrote it and yes, it is now in Ruby.

Monitoring API project is a multi-user programming interface designed to simplify the development of network monitoring software and allows users to express their monitoring needs in a device-independent way.
The main abstraction provided by MAPI is the network flow. Although flows have been used before in network monitoring systems, MAPI gives flows a first-class status. Applications that uses MAPI can specify what flows or flow statistics they are interested in by applying functions to flows.
A MAPI function can be a BPF filter, string search, packet counter or more advanced like a NetFlow generator. These function will automatically run in hardware if there is support for it on the hardware being used.
MAPI currently supports the following hardware:
- Normal NICs through libpcap
- DAG cards without co-processor
- SCAMPI adapter
Enhancements:
- This release includes support for distributed monitoring, several new MAPI functions, demo applications, and a lot of bugfixes.

Remote Monitoring Agent (RMA in short) is an auxiliary application for HostMonitor. Enterprise license for Advanced Host Monitor already includes license for 10 installations of the agent. Holders of a Lite, Standard or Professional licenses may buy an additional license for Remote Monitoring Agent separately.
HostMonitor 4.0+ can monitor remote networks using Remote Monitoring Agents (RMA). RMA is small application that accepts requests from HostMonitor, performs test and provides information about test result back to HostMonitor.
Why you may need RMA? Here are just several reasons:
RMA increases security of the network. When you have to run the tests such as CPU Usage test or Performance Counters tests on a remote Windows system, HostMonitor must be able to log in to that system with administrators privileges. Instead you may now use an agent installed on that remote system. In this case HostMonitor will not have to log on to that system at all. HostMonitor needs just one TCP port to communicate with the RMA agent (by default it uses #1055 port, however you may set an agent to use any other port).
Remote Monitoring Agent is also a very useful tool when you have to monitor two (or many) separated networks (connected through Internet). In this case installing just one instance of RMA behind the firewall in network "A" will allow to monitor entire network "A" using the HostMonitor located in the network "B" with just one open TCP port.
RMA decreases the network traffic. E.g. frequent use of "File Integrity" or "Compare Files" tests in an array of remote systems may apply significant load on the network. The more and the bigger files you test the more traffic increase you get. RMA runs locally and sends only the test results to the HostMonitor thus decreasing the amount of network traffic.
Remote Monitoring Agent simplifies network administration. You no longer need to share local drives/folders to perform tests such as File Integrity, Folder/File Size, File Availability, Count Files, etc
RMA for Linux / BSD / Solaris allows you to perform tests that HostMonitor cannot perform. For example HostMonitor cannot monitor processes that are running on Linux systems. RMA can do that.
Main features:
- All traffic between Remote Monitoring Agents and HostMonitor is encrypted.
- It is possible to customize the list of enabled tests for each of the agents (e.g. living only Count Files and UNC tests only).
- You can restrict incoming TCP connections with the list of acceptable addresses.
- With RMA Manager you may configure, restart and even upgrade agent(s) remotely.

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.

SNMP::Monitor is a Perl package for monitoring remote hosts via SNMP.

SYNOPSIS

require SNMP::Monitor;

# Read a configuration file
my $config = SNMP::Monitor->Configuration("/etc/snmpmon/config");

# Create a new monitor
my $monitor = SNMP::Monitor->new($config);

# Start monitoring (endless loop, never returns)
$monitor->Loop();

The SNMP::Monitor module is a package for checking and watching arbitrary values via SNMP. Events can be triggered, Logging can be done, whatever you want.

The package is based on the SNMP package, but it is merely created for system administrators and not for programmers.