Monitorix 1.4.0 Speaks Plaintext

Oct 06, 2009

The free software monitoring software Monitorix is available in version 1.4.0. New among the features is a plaintext version.

The Monitorix open source program in its standard views provides graphs for numerous computer performance values such as CPU load, Ethernet traffic, network services and hard disk usage. The diagrams rendered through RRDTool can be viewed on the Web as HTML pages. The data is now also available as plaintext, which makes things easier for seeing-impaired users and automated analysis.

Developers also implemented a new alert capability for Monitorix that reports on the last 15 minutes of average CPU load. They also resolved a CGI scripting bug that affected how CPU graphs were represented.

Monitorix 1.4.0 is under GPLv2 licensing and available for download on the project homepage as source code and in numerous packages.

Related content


  • Thanks for the response...

    I took a look at Monitorix and compared it with SysUsage. I have to agree that they monitor about the same things. Monitorix appears to come with prettier report pages by default. I'd definitely take a look at it first.

    SysUsage appears - at first glance - to include more time periods for the 20+ default items monitored. We did create static front-ends that drill down into the multitude of servers and merge the main items of concern for a single server before getting to the detailed Daily, Weekly, Monthly graphs for all the details.
  • Re: Any significant diff to SysUsage?

    I am not familiar with SysUsage. However, I have the impression that they monitor more or less the same parameters. Besides, they both use RRDTool. If you're happy with your current software, I see no reason to change.
  • Any significant diff to SysUsage?

    I've been happily using SysUsage to simple performance

    Is this tool comparable?
comments powered by Disqus
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters

Support Our Work

Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

Learn More