Free monitoring 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.

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.

Pandora are a Free Software set of programs, set under the GPL license, that allows to analyze in a visual way status and performance of several parameters from different Operating Systems, servers, applications and hardware systems as Firewalls, Proxies, Data Bases, Web Servers or Routers. All integrated into an open and distributed architecture.

Pandora can be deployed in every Operating System. You have an agent for every platform. Pandora can monitor hardware systems with TCP/IP Stack, as load balancers, routers, switches, printers and so on.

Pandora has six components: Pandora Data Server, Pandora Network Server, Pandora SNMP Console, Pandora Agents, Pandora Database and Pandora Web Management System (Web Console).

Pandora Servers and SNMP Console

They are the recipient of bundles of information and the generators of alerts; they are the brain of the system. We can have several servers for very big systems or a single server. They are developed in Perl and works under any platform, with the required modules. Nevertheless its "official" platform is GNU/Linux. They also insert the gathered data into the Database. You can have several Pandora Servers connected with the same Database.

Pandora Web Console

It allows to manage the system and to operate with it; its the user interface of Pandora. We can have several Web Consoles in the same implantation. It is developed in PHP and leans on a Data Base and a Web Server, being able to work in any platform: GNU/Linux, Solaris, Win2000, AIX and others.

Pandora Database

Core module of Pandora (as you can see in the architecture overview). In this database resides all the information of the enterprise, for example, all data gathered by agents, all configuration defined by administrator, all events, incidents, audit info... At this moment, only MySQL DataBase is supported. More Databases in the future.

Pandora Agents

They can monitor any numeric parameter, boolean states, strings or numerical incremental data and/or condition. They have a centralized architecture based on lightweight design for agents (shellscript, wsh, perl) and light agents to collect data. They support all type of platforms (Microsoft, AIX, Solaris, GNU/Linux, IPSO, FreeBSD, etc) because the agents are completely free software, and they communicate using SSH, FTP, NFS or other good way, using an XML container to transport data.

lm-monitor is a daemon that run sensors at a defined interval (15 seconds by default) and checks the output
If a sensor value has gone outside the defined limit since the last reading, an email message is sent to one or more administrators, alerting them about the condition so they can take appropriate action.
lm-monitor requires the lm-sensors package and a working email configuration, including the "mail" command.
Enhancements:
- Found and corrected a bug in MailText() that generated unvalid indices into SData member arrays.
- Wrote a script to create an unprivileged system account.
- Added code to drop root privilegies and run as the system account mentioned above.
- The install target creates a separate directory for lm-monitor in $(PIDDIR) (normally /var/run), and sets owner and group to lm-monitor. This is neccesary for lm-monitor to be able to remove the pidfile on exit, after having dropped root privilegies.
- Corrected the manpage regarding the --verify-config option.
- Added --help and --version as valid options (previously only -h and -v was accepted).
- Found and corrected a bug in EvaluateAlarm() where newBits was used instead of oldBits when composing mail messages for restored alarms.

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

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.