<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.0.10"> <TITLE>Message</TITLE> </HEAD> <BODY> Has any one done this for Big Sister? - Jamie On Wed, 2005-03-09 at 15:30, Williams, P. Lane wrote: <BLOCKQUOTE TYPE=CITE> <H1>Straight from my recommendation plan to my management....hope it helps............... Nagios vs. Big Brother</H1> Listed below are operational, administrative and service functionality features, in comparison, that set Nagios above Big Brother. A list, of these comparisons, is outlined in attachment 2 (Added features of Nagios over Big Brother). <H1> Operational Functionality</H1> Some of the operational functions that Nagios has built-in that Big Brother does not (all are accomplished through the user interface): <OL TYPE=1> <LI TYPE=1 VALUE=1>Ability to disable and enable host and service checks. <LI TYPE=1 VALUE=2>Ability to schedule impromptu downtime for services and host. <LI TYPE=1 VALUE=3>Ability to disable and enable host and service notifications. <LI TYPE=1 VALUE=4>Ability to schedule immediate service and host checks for active checks. <LI TYPE=1 VALUE=5>Ability to leave comments about a service or host. <LI TYPE=1 VALUE=6>Ability to easily acknowledge alerts. <LI TYPE=1 VALUE=7>Ability to restart the Nagios process. <LI TYPE=1 VALUE=8>Various other Nagios services can be controlled from the user interface. <LI TYPE=1 VALUE=9>Provides an overall view of the network hierarchy, which shows “parent-child” relation. <LI TYPE=1 VALUE=10>View configuration from the user interface. </OL> <H2>Administrative Functionality</H2> Some of the administrative functionality Nagios has built-in that Big Brother does not: <OL TYPE=1> <LI TYPE=1 VALUE=1>Ability to set host and service dependencies. Service and host dependencies are an advanced feature that allows you to control the behavior of hosts and services based on the status of one or more other hosts or services. </OL> <OL TYPE=1> <OL TYPE=a> <LI TYPE=a VALUE=1>A service can be dependent on one or more other services. <LI TYPE=a VALUE=2>A service can be dependent on services that are not associated with the same host. <LI TYPE=a VALUE=3>Service dependencies are not inherited. <LI TYPE=a VALUE=4>Service dependencies can be used to cause service execution and service notifications to be suppressed under different circumstances. </OL> </OL> <OL TYPE=1> <LI TYPE=1 VALUE=1>Template-based configuration files. The benefits of using the template-based config file format is that you can create object definitions that have some of their properties inherited from other object definitions. Template-based object definitions allow you to create large numbers of objects using just a small number of definitions in your config file(s). Nagios template-based configuration files are far superior to Big Brother configuration files in areas of configuring notifications, time frames, contacts, contact groups, host, host groups, service and host dependencies, command definitions, host and service escalations…etc. </OL> <OL TYPE=1> <LI TYPE=1 VALUE=1>The ability to set security and authorization of designated CGI’s and command functions. </OL> <OL TYPE=1> <LI TYPE=1 VALUE=1>A PHP (widely-used general-purpose scripting language) web interface has been developed to make changes to the configuration files. </OL> <H2>Service Functionality</H2> Some of the service functionality Nagios has built-in that Big Brother lacks or does not support: <OL TYPE=1> <LI TYPE=1 VALUE=1>Nagios supports event handlers. Event handlers are optional commands that are executed whenever a host or service state change occurs. An event handler could proactively fix problems, troubleshoot failures, or any myriad of customized events. </OL> <OL TYPE=1> <LI TYPE=1 VALUE=1>Nagios supports active service checks. Active service checks are initiated from the Nagios server, providing server-side network monitoring. </OL> <OL TYPE=1> <LI TYPE=1 VALUE=1>Nagios supports flap detection. Flapping occurs when a service or host changes state too frequently, resulting in a storm of problem and recovery notifications. Flapping can be indicative of configuration problems (i.e. thresholds set too low) or real network problems. When flap detection is enabled Nagios will suppress notifications, until flapping has stopped. </OL> <OL TYPE=1> <LI TYPE=1 VALUE=1>Nagios provides more flexible UNIX support. The UNIX (Sun, HP, Linux, Mac OSX, AIX…etc) clients provide both active and passive checks. Active checks are handled by the “nrpe” daemon and passive checks are handled by the “nsca” daemon. Client checks are handled by plugins. Plugins are scripted or compiled applications that gather information from the client. Client programs can be written to gather disk, cpu, memory, network, LDAP, database, web-server, or just about any metric you may wish to monitor. Nagios comes with pre-defined plugins that can be customized to meet any UNIX environment. </OL> <OL TYPE=1> <LI TYPE=1 VALUE=1>Nagios provides more flexible Microsoft support. The Microsoft client of choice is NSClient. NSClient provides support for disk, CPU, file age, services, processes, uptime, memory, and practically any available performance counter. NSClient does not currently support Event Log messages (in development). Not to worry, the power of PERL prevails. Using the PERL Net::Nsca module, a client side application can be written to capture Microsoft Event Log messages and send to the Nagios server as a passive check. Three other options are using SNMP or with some modification the “Event Catch” application Tim Dunlevy wrote or a UNIX syslog facility could be used as a viable Event Log reporting service for Nagios. Because of this versatility, monitored Event Log messages can be better defined. </OL> <OL TYPE=1> <LI TYPE=1 VALUE=1>Nagios supports notification escalations. Notification escalations are used to add additional contacts to service and host notifications if a problem persists. </OL> Example: After a problem with a service occurs a notification message will be sent to the individuals responsible for the administration of the specific server. If that problem persists, without acknowledgement, then after a predetermined number of notifications the server administrator(s) and a group of second-level individuals would be notified. This escalation process can continue for as many levels of notification that are needed to obtain a response to the alert. <OL TYPE=1> <LI TYPE=1 VALUE=1>Nagios supports logging of performance data. Performance data can be used to graph and report on system performance metrics. This service is useful for troubleshooting and trending possible problems. </OL> <OL TYPE=1> <LI TYPE=1 VALUE=1>Nagios supports the integration with other software such as Port sentry, RRDTool, MRTG…etc. </OL> <OL TYPE=1> <LI TYPE=1 VALUE=1>Nagios supports service check parallelization and service check interleaving. Parallelization means Nagios can spawn numerous checks at once on the monitoring server. Interleaving allows for a more even distribution of service checks, reduced load on remote hosts, and faster overall detection of host problems. </OL> Lane Williams Linux Systems Administrator ITSD/IDS Johns Hopkins University APL <BLOCKQUOTE> -----Original Message----- From: nagios-users-admin@lists.sourceforge.net [mailto:nagios-users-admin@lists.sourceforge.net] On Behalf Of Brent Ryan Sent: Wednesday, March 09, 2005 2:46 PM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Nagios Vs. Big Brother I know there is some obvious answers to this, but is there any documentation of pros/cons for these monitoring applications? Why is nagios better then Big Brother? Brent <DIV ALIGN=center></DIV> <DIV ALIGN=center>Don't miss the 2005 Blackboard Users Conference April 12-14 in Baltimore, MD! </DIV> <DIV ALIGN=center>Visit <A HREF="http://www.blackboard.com/about/events/BbUC05/index.htm">http://www.blackboard.com/about/events/BbUC05/index.htm</A> for more information.</DIV> This e-mail is intended only for the personal and confidential use of the recipient(s) named above. <DIV ALIGN=center>It may include Blackboard confidential and proprietary information, and is not for redistribution.</DIV> </BLOCKQUOTE> </BLOCKQUOTE> <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> -- Jamie Bohr <<A HREF="mailto:Jamie_Bohr@Agilent.com">Jamie_Bohr@Agilent.com</A>> </TD> </TR> </TABLE> </BODY> </HTML>