Free mrtg windows software for linux

Qmrtg is a modular tool to help monitoring the activity of a qmail server. Its intended to be used with MRTG. Each module carries out a different log analysis.
A super-module lets the user easily request any analysis without having to know anything about the modules themselves. It was originally written for qmail, but most of its modules work with any software using multilog (see daemontools). It is an alternative to qmailmrtg7.
Enhancements:
- autoconf and automake are now used.
- A bug in the concurrency analyzer that caused incorrect reports under some circumstances was fixed.
- The user documentation was revised along with the target description in the mrtg config file.

mrtg-ping-probe project monitors round trip time and packet loss to another host. Still on my TODO list: add own min/max/avg rtt calculation, add perl ping module, add rping and rsh support...
mrtg-ping-probe is a ping probe for MRTG 2.x. It is used to monitor the round trip time and packet loss to networked devices. MRTG uses its output to generate graphs visualizing minimum and maximum round trip times or packet loss.
mrtg-ping-probe depends on the following software being installed on your system: perl (at least version 5.6.1), mrtg (I use version 2.8.8, though any mrtg 2.x version should work), and a ping program that displays a summary of the round trip times upon termination or timeout.
mrtg-ping-probe runs on AIX, BSD/OS 2.1, FreeBSD/2.2.x, IRIX/6.2, Linux, Mac OS X (Darwin 5.4), NetBSD, OpenBSD, OS/2, OSF1 V3.2, Solaris 1.1.2 (SunOS 4.1.4), Solaris 2.5.1 (SunOS 5.5.1), Solaris 7 (SunOS 5.7), Solaris 8 (SunOS 5.8), Solaris 9 (SunOS 5.9), HP-UX 9, Windows 98, and Windows 2000 (english, french, portugesee, and spanish locales).
If you install the Windows ping program that comes with Windows 98, Windows 2000, or WinSock 2.x, mrtg-ping-probe will also run on Windows 95 and Windows 4.0.
Support for additional systems is usually easy to add, as described in the file INSTALL.
Act responsible: do not use mrtg-ping-probe to ping devices without the owners permission. Just imagine 10,000 people would decide to ping your hosts ... mrtg-ping-probe is meant to be used within your network to get round trip time performance figures for your network.
Usage: mrtg-ping-probe [-hsvV] [-d deadtime] [-k count] [-l length] [-o ping_options] [-p [factor*]{min|max|avg|loss|integer}/[factor*]{min|max|avg|loss|integer}] [-r [rsh:][user@]host[:osname]] [-t timeout] host
Enhancements:
- new platforms supported: italian Windows 2000 locale.
- bugfixes: on Windows actually return deadtime when we lost all packets, not 0. the ping child process should actually be killed now on Unix platforms.
- changes: ***** Possible Incompatability ***** raised minimum required perl version to 5.6.1. lots of typos fixed.

RRDBrowse is a poller daemon, templater and webinterface for RRDTool. It has a threaded daemon which periodically runs from cron. It works with small .nfo files which hold router information and optionally connection details, colors, min max, bandwidth settings, etc, etc. RRDBrowse uses a small caching mechanism to store interface names. Its like MRTG in actual state.
Main features:
- 100% Perl
- Extremely Simple Configuration.
- Flexible & Extendible using Simple and Small Perl modules.
- Caching of ifIndex tables and other slow data. Retrieve once, Process Multiple times.
- Its Fast, thanks to RRDTool! Large organizations can handle thousands updated items each run.
Enhancements:
- Added RT statistics module
- Added oidderive module from Ingimar Robertsson
- Added w2kcpu and w2kmem modules from Okumura Yoshifumi
- Cleanups in utilities and cgi
- Added option to specify your own stylesheet
- Added Limit option in ciscocpu
- Improved debugging facilities
- Added Linux Disk I/O Statistics
- Added Linux Open Files and Open Sockets stats

qmailmrtg7 uses qmails excellent and extensive logging via multilog, tcpserver and qmail-send. qmailmrtg7 takes the pop3 smtp and qmail transaction logs and sends them to 9 different mrtg graphs, each graph with 4 historical time series.
Main features:
- very fast - typically processes in less than 2 seconds
- Intelligently uses the multilog file name time stamp to determine which logs to open and process.
- Single small C program with no external dependances and simple command line options. See the qmail.mrtg.cfg for working examples of the options.
- Works on any system that supports qmail

mrtg-ntap-probe can probe for Network Appliance NetCache caching appliance and NetApp Filer.

mrtg-ntap-probe retrieves the disk and file (inode) utilization by volume or quota tree name, so you do not need to find the right OID, which might change over time as you add and/or remove volumes and quota trees.

You need a recent release of mrtg 2.x, perl 5.003 or better, a NetApp NetCache appliance with NetCache release 5.1 or better and/or a Network Appliance Filer running Data Ontap 6.0 or better.

If you have a Network Appliance service contract and access to their software tools library on now.netapp.com, you should also take a look at their mrtg-filer and mrtg-netcache packages!

MRTG::Parse is a Perl extension for parsing and utilizing the logfiles generated by the famous MRTG Tool.

SYNOPSIS

use strict;
use MRTG::Parse;

my $mrtg_logfile = "/var/www/htdocs/mrtg/eth0.log";
my $period = "day";
my $desired_unit = "GB";

my ($traffic_incoming, $traffic_outgoing, $traffic_sum) = mrtg_parse($mrtg_logfile, $period, $desired_unit);

print "Incoming Traffic: $traffic_incomingn";
print "Outgoing Traffic: $traffic_outgoingn";
print "= Sum $traffic_sumn";

This perl extension enables its users to parse and utilize the logfiles that are generated by the famous MRTG (Multi Router Traffic Grapher) tool.

mrtg_parse() takes three argument:

1st: filename of the mrtg logfile
2nd: time period to genereate the output for
valid values are:
- individual time periods like: 20040821-20050130 (ISO 8601)
- static values: day, month, year
3rd: the desired unit (optional)
valid values are:
- B, KB, MB, GB, TB
- if missing mrtg_parse will chose an adequate one for you
mrtg_parse() returns three values:

1st: Incoming traffic
2nd: Outgoing traffic
3rd: Sum of incoming and outgoing

MRTG::Config is a Perl module for parsing MRTG configuration files.

WARNING

This module, while reliable right now, is still in ALPHA stages of development... The API/methods may change. Behaviors of methods will almost certainly change. The internal structure of data will change, as will many other things.

I will try to always release working versions, but anyone who expects their code that uses this module to continue working shouldnt... until I remove this warning.

SYNOPSIS

Ever have the need to parse an MRTG config file? I have. I needed to parse lots and lots of them. Using the functions built-in to MRTG_lib was too slow, too complex, and used too much RAM and CPU time for my poor web server to handle - and the data structures MRTG_lib built were way more complex than I needed.

MRTG::Config can load and parse MRTG and MRTG-style confiuguration files very quickly, and the parsed directives, targets and values can be located, extracted, and manipulated through an OO interface.

This module is intended to focus on correctly parsing the format of an MRTG configuration, regardless of whether or not the directives and values, etc. are valid for MRTG. I am using both the parsing behavior of MRTG_libs readcfg() function and the description of the format on the MRTG website as my guidelines on how to correctly parse these configuration files. I am still a short way off that goal, but this module is currently being used in a production environment with great success!

PLEA FOR MERCY

I plan on adding to this documentation and making it better organized soon, but Im willing to answer questions directly in the mean time. Also, this is my first module, written in a hurry to appease some disgruntled engineers. I do plan on continuing to improve it, so any input, positive or negative is certainly welcome!

USAGE EXAMPLE

use MRTG::Config;

my $cfgFile = mrtg.cfg;
my $persist_file = mrtg.cfg.db;

my $mrtgCfg = new MRTG::Config;

$mrtgCfg->loadparse($cfgFile);

# Want to store the parsed data for use later or by
# another program?
$mrtgCfg->persist_file($persist_file);
$mrtgCfg->persist(1);

foreach my $tgtName (@{$mrtgCfg->targets()}) {
my $tgtCfg = $mrtgCfg->target($tgtName);
# Lets assume every target has a Title.
print $tgtCfg->{title} . "n";
}

# globals() has some, um, interesting things you
# should know. Please read about it below...
my $globalCfg = $mrtgCfg->globals();

# Lets assume WorkDir is set.
print $globalCfg->{workdir} . "n";