Free alchemy network monitor pro v7.78 software for linux

akk@da is a simple network monitoring system designed for small and medium size computer networks. Its purpose is to quick detect system or network faults, and to display information about detected problems for the administrator.
akk@da is designed as a pro-active network monitor. It does not wait for information from any agents, systems, etc. It collects information itself every minute (you can decrease this period to as little as 1 second if needed). Almost all services of the monitored hosts are discovered automatically.
Main features:
- monitoring of host availability, resources and network services (probes use SNMP, ICMP, raw TCP, SSL, DNS, UCDavis script extensions and many others for checking hosts health and collecting data)
- automatic discover of services available on host like CPU, RAM, network interfaces, disks, processes, etc, etc (you do not have to configure it manually, all you have to do is to add a new host (via web based GUI) and akk@da will discover its services for you)
- collecting performance data about monitored services (fully RRDTool integrated)
- services flaps detection
- possible adding you own probes
- easy way to add support to SNMP devices not supported by akk@da through the template based model
- easy to use web based GUI with support features like:
- alarms presentation with option to approve alarms
- filterable logs
- RRDTool based graphs with performance
- configuration of monitored services or hosts
- akk@da system status and management
- users and groups management
- rights management (you can manage right of the group to every single service if you need)
- tree based hosts organization - it allows organizing monitored resources in easy to browse and quick navigate schema
- views support (you can arrange monitored services in groups you need)
- displaying information in compact mode allows you to estimate the host health on first sight
- context menus available all the time allows quick access to necessary options, pages
- nice look icons which makes easy to identify host/service vendor, function and probe type
- web interface looks like standard MS Windows; all GUI written in DHTML & JavaScript - no applets, ActiveX controls and other strange modules.
Enhancements:
- This release fixes a major bug with ignoring discover excludes by the windows_service probe.

Nagios (formerly Netsaint) is a daemon written in C that is designed to monitor networked hosts and services.
Nagios project has the ability to notify contacts (via email, pager or other methods) when problems arise and are resolved. Host and service checks are performed by external "plugins", making it easy to write custom checks in your language of choice.
Several CGIs are included in order to allow you to view the current and historical status via a Web browser, and a WAP interface is also provided to allow you to acknowlege problems and disable notifications from an internet-ready cellphone.
Main features:
- Monitoring of network services (SMTP, POP3, HTTP, NNTP, PING, etc.)
- Monitoring of host resources (processor load, disk and memory usage, running processes, log files, etc.)
- Monitoring of environmental factors such as temperature
- Simple plugin design that allows users to easily develop their own host and service checks
- Ability to define network host hierarchy, allowing detection of and distinction between hosts that are down and those that are unreachable
- Contact notifications when service or host problems occur and get resolved (via email, pager, or other user-defined method)
- Optional escalation of host and service notifications to different contact groups
- Ability to define event handlers to be run during service or host events for proactive problem resolution
- Support for implementing redundant and distributed monitoring servers
- External command interface that allows on-the-fly modifications to be made to the monitoring and notification behavior through the use of event handlers, the web interface, and third-party applications
- Retention of host and service status across program restarts
- Scheduled downtime for suppressing host and service notifications during periods of planned outages
- Ability to acknowledge problems via the web interface
- Web interface for viewing current network status, notification and problem history, log file, etc.
- Simple authorization scheme that allows you restrict what users can see and do from the web interface
Enhancements:
- Fixed bug with processing epn directives in Perl plugins
- Fixed bug with check_result_path config option being ignored
- Added $MAXHOSTATTEMPTS$ and $MAXSERVICEATTEMPTS$ macros
- Fixed bug with incorrect output returned from embedded Perl plugins
- Fixed bug where status data file was not read by CGIs using mmap()
- Fix for CGI segfault
- Program status now updated at least every 5 seconds for addons that watch NDOUtils DB
- Added escape_html_tags option to CGI config file to escape HTML tags in plugin output
- Added optional integration with Splunk into the CGIs
- Added new action and notes URL target frame options to CGI config file
- Added new exclude option to timeperiod definitions for easy on-call rotation definitions

Netwatch is a Linux program created to aid in monitoring Network Connections. It is based on a program called "statnet" but has been substantially modified for its Ethernet emphasis. The project is a dynamic program which displays the Ethernet status based each the connections activity.
It has the capability of monitoring hundreds of site statistics simultaneously. The connections port number (Well Known Service) and destination address are available as well. There are options which allow router statistics to be measured on simple networks (with one router). External network communication is counted and transfer rates are displayed.
Main features:
- Reload feature for periodic saves and clears
- Routing Summaries with character graphics display
- Saves of Routing Statistics for last day of run (min. by min.)
- Freeze display (continue logging) for remote efficiency
- PPP Connectivity Monitoring
- Multiple Interface Support (1 at a time)

Autostatus is a network and server monitoring program. The project is designed to support large, arbitrarily complex networks of computers, and still provide feedback in a very timely fashion. To that extent, it has the following goals:
- Speed - Autostatus attempts to probe for network status as quickly as possible.
- Efficiency - Autostatus will not attempt to check for status on portions of the network it already knows are down, eliminating redundant checks.
- Accuracy - Autostatus presents as accurate a picture of the network status as it can from its perspective.
Autostatus has some features which make it fairly unique among network monitoring programs:
Dependency Resolution
Autostatus can be given information about the path it takes to reach network segments, or other dependencies in network or server topology. Given this dependency information, autostatus will then query for status in the proper order in order to guarantee that:
- Nothing is queried before all of the items upon which it depends have already been queried.
- Nothing is queried if an item upon which it depends is down.
- Items are not incorrectly marked as down when they are simply unreachable due to a dependency failure.
This dependency resolution is, of course, fully recursive. The software will also warn about abnormal conditions in the configuration file such as cyclical dependencies.
Parallel status gathering
Autostatus uses the excellent fping program written by Roland J. Schemers III at Stanford University. (see the fping copyright below). By intelligently grouping services together for parallel testing, Autostatus minimizes the amount of time necessary to scan large numbers of networks or servers.
For testing TCP services, Autostatus uses a component called tcpcheck to perform parallel checks of TCP connections. tcpcheck was developed specifically for Autostatus, but has considerable utility outside of Autostatus.
Status Web Page
Autostatus automatically generates a status web page which reflects the current-known network and server status on a per-item basis.
Email notification
Autostatus sends email when the state of a monitored item changes (based upon configurable thresholds). Using an email to pager program (such as hellpage, by the author, or various other paging programs), it is very easy to route notifications for each service to the correct party.
Multiple service monitoring
Autostatus can monitor both routers/hosts via ICMP messages, and specific services on machines via TCP connections. In keeping with the themes of autostatus, TCP connections may be avoided if the machine is not reachable via ICMP, or may be tried at all times.
Usage: tcpcheck < timeout > < host:port > [host:port]

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.

check_tcptraffic is a simple Nagios plugin to monitor network traffic on Linux systems.

Usage:

usage:
-c crit critical
-w warn warning
-i iface network interface
-r initialize
-v verbose

Netlogger is a project that consists of various UDP-based and broadcast-based network tools.
The netlogger package is an extremely lightweight toolset for basic network monitoring of a home network. It relies on features of the Linux kernel. The scripts that are included in the package rely on ettclsh (TCL 7.6 extended with a few low-level commands, including UDP support).
Enhancements:
- dont exit on EAGAIN
- made UDPBUFFER (size) depend on environment
- (main): same for UDPDELAY
- (main): added timing report if env(UDPVERBOSE)
- (main): added UDPSTRONG to setscheduler and mlock