The sys admin’s daily grind – Munin monitors SNMP-compatible devices

Good Substitute

Article from Issue 151/2013

What do you do if the Munin system monitoring tool does not have a native Munin client for a device? Sys admin Charly has a solution.

As you might remember from a previous article in this space, Munin is a two-part monitoring suite: On any device I want to monitor, I need to install the client, the “Munin node.” It constantly collects relevant data about the system on which it is installed. At certain intervals, the Munin server retrieves the collection and creates meaningful graphs from it with the help of RRDtool. This approach works well, and I have used Munin for many years, both privately and professionally.

At home, I have two devices that I cannot easily monitor with Munin: an older Cisco router from the 2600 series and a small NAS, by Synology, that provides home backup storage and acts as a DLNA server and data sink. The NAS runs a customized Linux, and on the manufacturer’s forums, people exchange ideas on running a Munin node.

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy Linux Magazine

Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • Charly's Column

    Ornithologists already know that magpies don’t really deserve their reputation. The true kleptomaniac in the world of birds is the raven. And it’s worthwhile for data dealers to make the acquaintance of Munin, a monitoring tool named after one fabled raven.

  • Building a Munin Plugin

    Munin collects information and plots parameters of your choice automatically and with minimal configuration. But if you can't find a plugin that captures the data you want to graph, you might have to roll your own.

  • darkstat

    Thanks to its minimal footprint, 20-year-old darkstat hardly generates any noticeable load even on low-powered systems, making it the perfect monitoring tool for Charly's home utility room.

  • The sys admin's daily grind: systemd-analyze

    In sys admin columnist Charly's case, no fumbled system startup goes undetected. This was already the case with SysVinit and has not changed with systemd. In terms of the his analysis tools, no stopwatch goes unturned.

  • Automation Tips and Tricks

    We asked some of our authors to share their favorite automation tricks.

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