From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2D25C1381F3 for ; Tue, 17 Sep 2013 06:35:36 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 18702E0A8F; Tue, 17 Sep 2013 06:35:29 +0000 (UTC) Received: from mail-qc0-f179.google.com (mail-qc0-f179.google.com [209.85.216.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 27792E0A6C for ; Tue, 17 Sep 2013 06:35:27 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id l4so3394718qcv.10 for ; Mon, 16 Sep 2013 23:35:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=brAhm6NtpQj1rkzppNJYX8ta/BdaqjOH6Vj0Qxfgj34=; b=h2iZmEctgZN1oN9Vwr4biKgE4P2s+NeA6bzvwfx8jMod7Pom3+I3VkajAbQM68wVwk UfBhMDU4MAlslz1/fSboUNRR2+TGwnAxG/ugtxFj+cWxzhvrPiQ/EmIs7T18aaCQBnRI 3NPp05Otfs6h9Y71vIxxzcMqF7zhLUGVU46cicFIlKZ1j4IaAPX94E/8BiULOX1Gfh3W /LlBxQOHcU7hszCgwK4YtSrX1P4WBGY0XK5LJrR34YII1NJScCOvW4LQ/b3snyY85kFR WArF0EZj9Vw8W6fPS0Kexq4RhexPC9rZMeMuVAOe/cy7wSekr8sJRzON5cK7oxv2JcCG m+Dg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.224.147.208 with SMTP id m16mr3966544qav.3.1379399727299; Mon, 16 Sep 2013 23:35:27 -0700 (PDT) Received: by 10.140.25.83 with HTTP; Mon, 16 Sep 2013 23:35:27 -0700 (PDT) In-Reply-To: <5237F12F.8070700@gmail.com> References: <5237F12F.8070700@gmail.com> Date: Mon, 16 Sep 2013 23:35:27 -0700 Message-ID: Subject: Re: [gentoo-user] Re: {OT} tried Nimsoft Monitoring? From: Grant To: Gentoo mailing list Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 7c073e31-1f8f-4a8c-9ef9-522862b0312a X-Archives-Hash: 4bbab6f7e481b2456aad33a48839dc23 > Munin and jffnms bear no real relation to each other. Yes they are > similar in that both can draw graphs but that's about where the > similarity ends. > > Munin's job is to periodically poll a device using whatever means is > available and gather data from the device. The data is always in the > form of a number - it measures something. The data can be anything you > can generate a number for - logged in users, traffic through an > interface, load, number of database queries. The list is endless. Point > being, the device/computer/hosts reports it's own numbers to munin, and > munin draws graphs. Munin does not record state, it has no idea what the > state of something is. > > Nagios is a problem child, it does not do what people assume it does (I > have constant fights about this at work). Nagios is a state monitoring > and reporting engine (simply because this is what it does well and > everything else it does it does poorly). Nagios will track if things are > up or down, if you acknowledged the condition and when, who to notify > when state changes (sms, mail, dashboard etc etc). > > What Nagios does poorly (despite this being it's advertised purpose) is > getting state events into the system. It really really sucks at this and > is coded from an extremely narrow point of view. Which explains the > numerous forks around (they all implement vital real world features that > Ethan refuses to commit). > > jffnms is something I don't use myself, but it looks like the same class > of app as Nagios. Don't be fooled into choosing between munin and > nagios/jffnms - they are not the same thing, not even close. Use both. Understood. Thank you James and Alan. - Grant