Monitorix 3.10.1 Released – A Lightweight System and Network Monitoring Tool for Linux

Monitorix is an open source, free and most powerful lightweight tool designed to monitor system and network resources in Linux. It regularly collects system and network data and display the information in graphs using its own web interface. Monitorix allows to monitor overall system performance and also help in detecting bottlenecks, failures, unwanted long response times and other abnormal activities.

Linux System and Network Monitoring Tool
Monitorix – Linux System and Network Monitoring Tool

It is written in Perl language and licensed under the terms of GNU (General Public License) as published by the FSP (Free Software Foundation). It uses RRDtool to generate graphs and display them using web interface.

This tool is specifically created for monitoring Red Hat, CentOS, Fedora based Linux systems, but today it runs on many different flavors of GNU/Linux distributions and even it runs on UNIX systems like OpenBSD, NetBSD and FreeBSD.

The development of Monitorix is currently in active state and adding new features, new graphs, new updates and fixing bugs to offer a great tool for Linux system/network administration.

Monitorix Features

  1. System load average, active processes, per-processor kernel usage, global kernel usage and memory allocation.
  2. Monitors Disk drive temperatures and health.
  3. Filesystem usage and I/O activity of filesystems.
  4. Network traffic usage up to 10 network devices.
  5. System services including SSH, FTP, Vsftpd, ProFTP, SMTP, POP3, IMAP, POP3, VirusMail and Spam.
  6. MTA Mail statistics including input and output connections.
  7. Network port traffic including TCP, UDP, etc.
  8. FTP statistics with log file formats of FTP servers.
  9. Apache statistics of local or remote servers.
  10. MySQL statistics of local or remote servers.
  11. Squid Proxy Web Cache statistics.
  12. Fail2ban statistics.
  13. Monitor remote servers (Multihost).
  14. Ability to view statistics in graphs or in plain text tables per day, week, month or year.
  15. Ability to zoom graphs for better view.
  16. Ability to define the number of graphs per row.
  17. Built-in HTTP server.

For a full list of new features and updates, please check out the official feature page.

Installing Monitorix on a RHEL/CentOS/Fedora Linux

First, install following required packages.

# yum install rrdtool rrdtool-perl perl-libwww-perl perl-MailTools perl-MIME-Lite perl-CGI perl-DBI perl-XML-Simple perl-Config-General perl-HTTP-Server-Simple perl-IO-Socket-SSL wget

If in case yum fails to installing one or more of above packages, then you could enable following additional repositories to install them.

  1. Enable EPEL repository
  2. Enable RPMforge repository

Next, download the latest version of ‘Monitorix‘ package using wget command.

# wget

Once successfully downloaded, install it using the rpm command.

# rpm -ivh monitorix-3.10.1-1.noarch.rpm
Preparing...                ########################################### [100%]
   1:monitorix              ########################################### [100%]

Once successfully installed, please have a look at the main configuration file ‘/etc/monitorix.conf‘ to add some extra settings according to your system and enable or disable graphs.

Finally, add Monitorix service to system start-up and start the service with following commands.

# chkconfig --level 35 monitorix on
# service monitorix start        
# systemctl start monitorix       [On RHEL/CentOS 7 and Fedora 22+ versions ]

Once, you’ve started service, the program will start collecting system information according to configuration set in ‘/etc/monitorix.conf‘ file, and after few minutes you will start seeing system graphs from your browser at.


If you have SELinux in enabled state, then graphs are not visible and you will get tons of error messages in ‘/var/log/messages‘ or ‘/var/log/audit/audit.log‘ file about access denied to RRD database files. To get rid of such errors messages and visible graphs, you need to disable SELinux.

To Turn Off SELinux, simple changing the line “enforcing” to “disabled” in ‘/etc/selinux/config’ file.


The above will disable SELinux temporarily, until you reboot the machine. If you want the system to start in always disable mode, you need to reboot the system.

Installing Monitorix on a Ubuntu/Debian/Linux Mint

The Monitorix installation can be done in two-ways, using Izzy repository for automatic installation/updates and another using manually download and install .deb package.

The Izzy repository is an experimental repository but the packages from this repository should work on all versions of Ubuntu, Debian, etc. However, no warranties are given – So, the risk is all yours. If you still want to add this repository for automatic updates via apt-get, simply follow the steps provided below for automatic installation.

Automatic Installation Using Izzy Repository

Add the following line to your ‘/etc/apt/sources.list’ file.

deb generic universe

Get GPG key for this repository, you can get it using wget command.

# wget

Once downloaded, add this GPG key to apt configuration by using the command ‘apt-key‘ as shown below.

# apt-key add izzysoft.asc

Finally, install the package via the repository.

# apt-get update
# apt-get install monitorix

Manual Installation Using .Deb Package

Manually, downloading latest version of .deb package and install it with taking care of required dependencies as shown below.

# apt-get update
# apt-get install rrdtool perl libwww-perl libmailtools-perl libmime-lite-perl librrds-perl libdbi-perl libxml-simple-perl libhttp-server-simple-perl libconfig-general-perl libio-socket-ssl-perl
# wget
# dpkg -i monitorix_3.10.1-izzy1_all.deb

During installation, a web server configuration takes place. So, you need to reload the Apache web server to reflect new configuration.

# service apache2 restart         [On SysVinit]
# systemctl restart apache2       [On SystemD]

Monitorix comes with a default configuration, if you wish to change or adjust some settings take a look at the configuration file at ‘/etc/monitorix.conf‘. Once you’ve done changes reload the service for new configuration to take effect.

# service monitorix restart         [On SysVinit]
# systemctl restart monitorix       [On SystemD]

Now point your browser to ‘http://localhost:8080/monitorix‘ and start watching graphs of your system. It can be accessed from localhost only, if you wish to allow access to remote IP’s. Simply open the ‘/etc/apache2/conf.d/monitorix.conf‘ file and add IP’s to the ‘Allow from‘ clause. For example see below.

<Directory /usr/share/monitorix/cgi-bin/>
        DirectoryIndex monitorix.cgi
        Options ExecCGI
        Order Deny,Allow
        Deny from all
        Allow from

After you made changes to above configuration, do not forget to restart Apache.

# service apache2 restart         [On SysVinit]
# systemctl restart apache2       [On SystemD]

Monitorix Screenshots

Please check out the following are some screenshots.

Monitorix Homepage

Monitorix Homepage
Monitorix Homepage

Monitor Linux Load Average

System load average, active processes and memory allocation.
System load average, active processes and memory allocation.

Monitor Linux Kernel Usage

Global kernel usage
Global kernel usage

Monitor Linux Kernel Processor

Per-processor kernel usage.
Per-processor kernel usage.

Monitor Linux Disk Health

Disk drive temperatures and health.
Disk drive temperatures and health.

Monitor Linux Filesystem and Disk I/O Read

Filesystem usage and I/O activity.
Filesystem usage and I/O activity.

Monitor Linux Network Traffic

eth0 interface traffic
eth0 interface traffic

Monitor Linux System Services

System services demand
System services demand

Monitor Linux Network Port Traffic

Network Port Traffic
Network Port Traffic

Monitor Linux Apache Statistics

Apache Statistics
Apache Statistics

Monitor MySQL/MariaDB Statistics

MySQL Statistics
MySQL Statistics

Reference Links:

  1. Monitorix Homepage
  2. Monitorix Documentation
If you liked this article, then do subscribe to email alerts for Linux tutorials. If you have any questions or doubts? do ask for help in the comments section.

If You Appreciate What We Do Here On TecMint, You Should Consider:

TecMint is the fastest growing and most trusted community site for any kind of Linux Articles, Guides and Books on the web. Millions of people visit TecMint! to search or browse the thousands of published articles available FREELY to all.

If you like what you are reading, please consider buying us a coffee ( or 2 ) as a token of appreciation.

Support Us

We are thankful for your never ending support.

28 thoughts on “Monitorix 3.10.1 Released – A Lightweight System and Network Monitoring Tool for Linux”

  1. Hello everybody,

    It is possible that someone is interested in knowing the existence of this Network Monitoring Tool: Pandora FMS Enterprise

    Best regards.

  2. Note that if you want to enable password protection (via the built-in webserver) you have to explicitly use the crypt function with htpasswd command, e.g.

    # htpasswd -c -d /var/lib/monitorix/htpasswd someusername

    without the -d it will use the default algorithm and that fails when authenticating on the browser.

  3. [[email protected] Desktop]# yum install /tmp/monitorix-3.6.0-1.noarch.rpm
    Loaded plugins: refresh-packagekit, rhnplugin
    This system is not registered with RHN.
    RHN support will be disabled.
    Setting up Install Process
    Examining /tmp/monitorix-3.6.0-1.noarch.rpm: monitorix-3.6.0-1.noarch
    Marking /tmp/monitorix-3.6.0-1.noarch.rpm to be installed
    Resolving Dependencies
    –> Running transaction check
    —> Package monitorix.noarch 0:3.6.0-1 set to be updated
    –> Processing Dependency: perl(MIME::Lite) for package: monitorix-3.6.0-1.noarch
    –> Processing Dependency: perl(RRDs) for package: monitorix-3.6.0-1.noarch
    –> Processing Dependency: perl-MIME-Lite for package: monitorix-3.6.0-1.noarch
    –> Running transaction check
    —> Package monitorix.noarch 0:3.6.0-1 set to be updated
    –> Processing Dependency: perl(RRDs) for package: monitorix-3.6.0-1.noarch
    —> Package perl-MIME-Lite.noarch 0:3.027-2.el6 set to be updated
    –> Processing Dependency: perl(MIME::Types) >= 1.28 for package: perl-MIME-Lite-3.027-2.el6.noarch
    –> Running transaction check
    —> Package monitorix.noarch 0:3.6.0-1 set to be updated
    –> Processing Dependency: perl(RRDs) for package: monitorix-3.6.0-1.noarch
    —> Package perl-MIME-Types.noarch 0:1.28-2.el6 set to be updated
    –> Finished Dependency Resolution
    Error: Package: monitorix-3.6.0-1.noarch (/monitorix-3.6.0-1.noarch)
    Requires: perl(RRDs)
    You could try using –skip-broken to work around the problem
    You could try running: rpm -Va –nofiles –nodigest
    [[email protected] Desktop]#

        • @Koshal,
          That’s good to hear, finally it worked for you..may I know on which distro you’ve tired latest version of Monitorix? Could you please share the steps with us so that we can update the article to latest version..

  4. Well, we actually used some of the mentioned tools. And we ended up using
    CloudView NMS . We run it on Ubuntu, but it can run on any Linux. Seems like it can monitor/manage practically anything: SNMP, sysLog TL1, services, web access, servers…). They discovered our network put in maps (they use Google maps). Secure multi-user web access with configurable profiles . Alarms forwarding via many protocols (including e-mail) They claim it scalable to thousands of nodes (we have 245 so far) and unlike others they do not charge as your network grows – from my point of view very important feature :-). Remote HTML-5 based interface from anywhere including mobile devices. The only caveat: manual is not that good, but they have very enthusiastic e-mail support. They added some specific feature for us in several days

  5. Just installed monitorix and found out that it is exposed to open world!!! Huge security risk here guys. I thougt it was safe and as this turtorial says that one should allow access manually because it is only opened for local host by default, is just bogus. I have tried to close down the access other than from localhost, but it is still open!

  6. Hi
    I have installed and configured monitorix . I am able to view http://localhost/monitorix/ page but can’t view graph following error iam getting

    (Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log. )

    Can please help me…..?

  7. Can someone please explain why we’re still publishing how-to articles with SECURITY DISABLING steps in them?! SELinux has been around for a long time, with plenty of documentation. As an industry, taking something that’s designed to make a system more secure and announcing to the world we’re purposefully disabling it rather than taking the time to learn why it’s restricting something seems rather foolish.

      • 1. Nagios monitors all your services on the network rather than just the single host that it is on.

        2. Nagios has significant amounts of documentation. This book is VERY detailed:
        but you can of course use the website for a lot of docs.

        3. Nagios is clever enough to work out whether just a service is down instead of a host, or whether it is likely that a switch is down, rather than the hosts themselves, which helps admins get to the real issue rather than having a lot of warnings that don’t directly tell you the real issue.

        4. The way Nagios works means that it is fairly easy to create a ‘plugin’ for it, and as a side effect means that there are already lots of ‘plugins’ available for it.

        • I say, if you have one or two servers, use Monitorix (easy to set up – took me two minutes), if you have a farm of servers, use Nagios.

          • I say, if you have a farm of servers, or multiple farms of servers use Zabbix over Nagios. Scales better and is easier to make custom monitoring and triggers, etc. Not that it’s particular hard in Nagios, but it’s even it easier in Zabbix.

          • @ John
            Thanks! I do have a farm of servers/network to manage. I had not heard of Zabbix before and from the 5 minutes spent looking at it, it does appear ‘more polished’ than nagios. I will compare the two in more detail.

          • With a farm of servers, You should probably checkout Recently found out about it. Setup is a cake walk, its free and it caters to all system monitoring requirements from top CPU taking processes, memory, disk usage, to network summary, everything I need. Hope you find it useful! :)

Got something to say? Join the discussion.

Have a question or suggestion? Please leave a comment to start the discussion. Please keep in mind that all comments are moderated and your email address will NOT be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.