Free monitoring tools for servers software for linux

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.

Postfix SMTP Monitoring Solution is a set of three Perl CGI scripts used to monitor the SMTP queue, allowing the deletion of messages that for one reason or another become "stuck" in the queue.

I needed a web-based solution to monitor my Postfix SMTP relay, which enabled me to remove messages that become "stuck" in the queue. I wrote three simple Perl scripts, and used Sudo to give me the desired functionality.

I am uploading these scripts in case they are useful to others. Assuming you have Apache configured correctly on your Postfix server, it should be as easy as placing the three .cgi files into your webservers cgi-bin directory, and making the appropriate modifications to your /etc/sudoers file (see the README contained in the tarball).

Network UPS Tools is a collection of programs which provide a common interface for monitoring and administering UPS hardware. Network UPS Tools uses a layered approach to connect all of the parts.
Drivers are provided for a wide assortment of equipment. They understand the specific language of each UPS and map it back to a compatibility layer.
This means both an expensive "smart" protocol UPS and a simple "power strip" model can be handled transparently.
This information is cached by the network server upsd, which then answers queries from the clients. upsd contains a number of access control features to limit the abilities of the clients. Only authorized hosts may monitor or control your UPS hardware if you wish.
Since the notion of monitoring over the network is built into the software, you can hang many systems off one large UPS and they will all shut down together.
Clients such as upsmon check on the status of the hardware and do things when necessary. The most important task is shutting down the operating system cleanly before the UPS runs out of power.
Other programs are also provided to log UPS status regularly, monitor status through your web browser, and more.
Enhancements:
- HAL support. IPv6 support.
- Support for many new devices.
- Many driver improvements.
- This release uses automake.

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.

NoMachine NX Server Manager is the upcoming management interface for the NX Terminal Server system.
The NX Server Manager is the easy-to-use NoMachine graphical administration interface for Unix systems that allows administrators to configure, manage and monitor the NX servers across a world-wide network.
The NX Server Manager is an add-on to the NX Server Enterprise and Small Business Edition, provided at no extra cost.
The NX Server Manager sports most of the features you would expect from an enterprise-grade application, with the easiness of use of a Web interface.
NoMachine NX is a fast terminal server system based on the X11 protocol. In addition, NX also translates and embeds the MS Windows Terminal Server and VNC protocols into X/NX.
By embedding RDP and RFB, it enables users to compress and accelerate remote Windows and VNC sessions. NX lets you work fluently even across slow links like modems.
The NX project provides a suite of libraries and X11 proxying agents implementing efficient compression and optimized transport of X11, SMB, IPP, HTTP, and arbitrary protocols like audio over the Internet.
Enhancements:
- This release provides fixes for a number of problems: the NX Server Manager setup script looked for a nonexistant file during the install or upgrade procedure, reloading the NX statistics Web page may have failed, and NX Server Manager may have provided a misleading message when NX statistics couldnt be generated.

KLCMonitorApplet provides a LineControl monitoring applet for Kicker.
KLCMonitorApplet is KDE applet that monitors a LineControl server, a program that controls your Internet connection.
Why did we code LineControl?
We were tired of using telnet to get a masquerading servers internet connection up and down. Furthermore you get clean statistics and you have better control over the line when youre not alone.
User accounting and the possibility to choose one from multiple lines/providers are two of the features that help to have an easy control over your connections.
What does LineControl do?
LineControl runs a server application on a masquerading - server (Linux). Clients on other hosts may now talk to this server and say that it should establish a certain line (usually using pppd/chat, isdnctrl or some other script). LineControl Server then calls a certain shellscript and waits until a specified network - device is up (for analog lines), until /dev/isdninfo changes its status (if using the ISDN capabilities) or until a certain file exists. Then it sends to all connected Clients a message that the connection is established.
The connection wont get killed until each client told to do so, had a timeout or has been terminated.
Main features:
- user accounting using Linux-PAM or passwd/shadow file
- controlling multiple lines
- throughput measuring
- logging & analizing (view example)
- logging to a MySQL database (view example)
- html formatted status report via webserver (view example)
- different line types (analog, isdn, adsl, ... it should be possible to run LC with any line!)
- pinger (to avoid line-drops)
- reporting data (time, nr, ...) about incoming isdn calls to the clients (inclusive addressbook lookup)
- client dependant modifications of the NAT servers firewall (using an external script whenever a client goes on- or offline)
Package description
linesrv The one and only LineControl Server. You certainly need it. Of course it runs only under linux.
wlc2 The standard client for Windows. Try the dynamic version. The chance that it runs on your system is quite small. If it doesnt work, then take the static version which includes some borland libraries. Functionality is all the same (including features and bugs).
klcc The one and only client for Linux KDE. High quality, KDE users will like the smooth integration into their desktop.
jlc A client written in Java. It hasnt many features yet but provides an application as well as an applet.
xlc A client for linux X11 using the Gimp Toolkit (gtk).
The gui is quite clobby but shows all lines and their statistics at the same time in a list. It includes xlcm, which consists only of the minidisplay from xlc.
lclog-mysql Some php scripts which generate nice statistics from a linesrv mysql log database if used together with a webserver such as apache.
lclog2mysql Helps converting a 2.1.x linesrv logfile to a mysql log. You still have to manually create the needed database and tables!

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.