Mapping options.

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Luis Fernando Lacayo
> Sent: Friday, January 18, 2008 8:47 AM
> To: Nagios Users
> Subject: [Nagios-users] Mapping options.
> 
> Good Day to all,
> 
> I finally got my NAGIOS setup pretty much the way that I like it.  I
am
> monitoring over 1000 devices, and I have 2 questions.
> 
> 1. When displaying the host group summary is there a way to group /sub
> group the display.  For example at the moment I have 6 different type
of
> Microsoft 2003 Servers.  I have a group for exchange, a group for AD,
> Ishare, etc.  A group of Linux boxes, HPUX, SUN and AIX.  What I would
> like to do is to have a summary that would only give me the servers by
> type, then a summary of the functions. Has anyone done this or some
> thing similar.

Sounds like hostgroups{} to group by type of box and servicegroups{} to
group by services provided. There is no 'nesting' capability. Am I
mis-interpreting?
 
> 2. The Status Map, for the number of devices that I am monitoring when
I
> click on the status map, I get a "BLOB", icons on top of icons, etc.
> Any way to clean this up?

Change the layout type or use a custom cords per object (hostextinfo{}).
With that many hosts though, you'll be challenged. Setting proper
parent's relationships will help. We have about 3000 devices and there
just isn't enough useful information in those maps to make that process
worthwhile for us so I don't have a whole lot of experience with it.

--
Marc


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null