Free argus monitoring system 3.5 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.

Orange Monitor is a system monitoring theme for SuperKaramba.
Main features:
- CPU Load and Temperature (mbmon)
- Used RAM
- Used Space on hda and hda2 (customizable)
- Bandwidth Spent (bars are customizable , Incoming gets full @ 1GB and Outgoing @ 256MB by default)
- XMMS Controls (xmmsctrl)
Inspired on:
- Yaxay Skin for Winamp3
- Pod Icons for LiquidWeather karamba
- SystemTux Karamba

Hardware Monitor is a multi-purpose, beautiful system-monitoring applet.
The Hardware Monitor applet is an applet for the GNOME panel which tries to be a beautiful all-around solution to system monitoring. It also strives to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your GNOME desktop.
Includes different viewers, including a flame effect, allows multiple devices to be monitored in the samme applet, uses smooth updating, polished graphs, clean HIG-compliant interface.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors

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.

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.

Nelisys project is Open Source Web-based Management System, to manage and monitor system and network including Router, Switch, Wi-Fi Access Point, Server, Networking services, etc.

There are performance and fault management function.

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.

The smartmontools package contains two utility programs (smartctl and smartd) to control and monitor storage systems using the Self-Monitoring, Analysis and Reporting Technology System (SMART) built into most modern ATA and SCSI hard disks. In many cases, these utilities will provide advanced warning of disk degradation and failure.

The suite of smartmontools contains two utilities:

smartctl is a command line utility designed to perform S.M.A.R.T. tasks such as disk self-checks, and to report the S.M.A.R.T. status of the disk.

smartd is a daemon that periodically monitors S.M.A.R.T. status and reports errors and changes in S.M.A.R.T. attributes to syslog.