Free monitoring software software for linux

Argus Monitoring System software is a system and network monitoring application.
It will monitor nearly anything you ask it to monitor (TCP + UDP applications, IP connectivity, SNMP OIDS, Programs, Databases, etc).
It presents a nice clean, easy to view web interface that will keep both the managers happy (Red Bad. Green Good.) and the techs happy ("Ah! thats what the problem is").
It can send alerts numerous ways (such as via pager) and can automatically escalate if someone falls asleep.
Main features:
- It is open-source available at no charge.
- It has a clean and intuitive web interface.
- The web pages can easily be understood by non-technical people.
- It can generate graphs of what is going on.
- It can monitor network connectivity (Ping test)
- It can monitor TCP/UDP ports
- It can monitor a wide variety of TCP/UDP applications (HTTP, SMTP, RADIUS, ...)
- It can monitor the output or exit code of a program (Program test)
- It can monitor the content of a web page (such as a shopping cart application)
- It can monitor the authoritativeness of a nameserver
- It can monitor SNMP OIDs (such as BGP status, UPS voltage, room temperature, ...)
- It can monitor the results of SQL queries
- It can monitor itself.
- It can be extended to monitor things that the author didnt think of
- It can notify someone (or many people) when something happens
- It can escalate, and notify someone else, if things dont get fixed.
- It can not alarm for known downtime (maintenance overrides)
- It will summarize and rate-limit multiple notifications to prevent paging-floods.
- It keeps historical statistics, for analysis or SLA verification.
- It scales well and can monitor many, many things.
- It can restrict users to viewing only certain items (user "views")
- It can restrict users access to certain features (access control)
- It can support IPv6.
- It can support SNMPv3.
- It can support l10n for your native language.
- It can support redundant multi-server configurations.
Enhancements:
- This release offers improved performance and scalability, adds support for additional tests, and adds support for failover and redundancy.

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.

Cimon is Perl program wich monitors the load (memory and CPU) on Cisco routers using SNMP, and generates graphics with statistics using rrdtool. Its good for information about your routers health.

It monitors and displays the cpu 5 minutes utilization in percents and free+used Processor memory. The I/O memory(usualy 2 MB) or Fast on high end routers is being monitored too, but there isnt graphic for it. Cimon is good source for information about your routers health. From version 0.2 cimon can do ip accounting using the cisco ip accounting feature.
The logfiles that it generates as the rrd files needed for the graphics are fully compatible with those produced by sasacct (SASs accounting statistics). So you can use its cgi interface also its posibility to generate graphics on demand or on a user defined interval (via crontab and -g option).

Nmonitor is a monitoring tool, by default capable of monitoring via ping, UDP and TCP checks.
It has builtin plugin system so customized scripts can be used to monitor whatever you like eg. oracle tablespaces, diskspace whatever.
This tool was written because I needed a very simple network monitor, and thats what it is, dont expect any miracles from this thing.
Enhancements:
- No extra features, just some bugfixes
- reporting bug fixed
- alarm causes nmonitor to be locked bug fixed
- some other minor stuff I cant remember
- removed some typos from INSTALL doc:)

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.

Linux monitor checks processes, disk space, load avarage and monitors syslog of its host machine at user given intervals, and reports errors to syslog or via the Linux Monitor server. If no interval is given default(15 mins) is used.

Installation:

The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.

It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.

Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, a file `config.cache that saves the results of its tests to speed up
reconfiguring, and a file `config.log containing compiler output (useful mainly for debugging `configure).

If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.

If at some point `config.cache contains results you dont want to keep, you may remove or edit it.

The file `configure.in is used to create `configure by a program called `autoconf. You only need `configure.in if you want to change it or regenerate `configure using a newer version of `autoconf.

The simplest way to compile this package is:

1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.

If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.

Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.

2. Type `make to compile the package.

3. Optionally, type `make check to run any self-tests that come with the package.

4. Type `make install to install the programs and any data files and documentation.

5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.

There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with 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.