[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nagios-users
Subject:    [Nagios-users] RES:  Status Map / NOC Screens
From:       "Dario B. Bestetti" <dario.bestetti () opservices ! com ! br>
Date:       2007-08-30 14:57:09
Message-ID: 018e01c7eb16$0a4c2a00$1ee47e00$ () bestetti () opservices ! com ! br
[Download RAW message or body]

Giles, try this project: http://nexsm.sourceforge.net/

[]s
_________________________________________________
Dario B. Bestetti        OpServices
                                  R. Luciana de Abreu, 471 - Sala 403
                                  Porto Alegre, RS - CEP 90570-060
Fone 55(51)30613588 Mobile  55(51)81518218 
Fax     55(51)30613588  Email    dario.bestetti@opservices.com.br 
 
               "In God we trust, the rest we monitor ..."
_________________________________________________



-----Mensagem original-----
De: nagios-users-bounces@lists.sourceforge.net \
[mailto:nagios-users-bounces@lists.sourceforge.net] Em nome de Giles Coochey Enviada \
                em: quinta-feira, 30 de agosto de 2007 04:38
Para: nagios-users@lists.sourceforge.net
Assunto: [Nagios-users] Status Map / NOC Screens

Hello List,

I've had a bit of a google and look through the archives, and haven't found much that \
will help me on this, so I thought I'd put something to the list:

I'm currently working on user co-ordinates for the status map. It's an annoying and \
fidgety task to get everything positioned correctly. I did come across a Linux tool \
which seemed to be able to help, but unfortunately it required a UNIX GUI, which I \
don't have access to.

So, what techniques and tools have you used in design and positioning of items on the \
statusmap?

I'm currently resorting to using Visio to move text boxes around, each representing a \
host on the statusmap - having set the page size to around the resolution that will \
be used in our NOC, but it's still quite a fiddle and I still have to manually go \
through my configuration files entering the appropriate co-ordinates. Another issue \
is that Visio's origin is on the bottom right of the screen, while Nagios's origin is \
on the top right of the screen, meaning that the status map is inverted vertically \
when put into Nagios from Visio (not a huge problem).

I am intending to use the link:

http://nagioshost/nagios/cgi-bin/statusmap.cgi?createimage

on a full screen browser Window (like Kiosk-Mode) for our NOC, it looks like I will \
have to embed this to get the page to refresh, plus it also seems that the background \
will need some work to make it look nice, it would be good to hear if anyone has had \
experience down this route as well and has any advice, or alternatives to suggest?

We will also have the tactical overview in the NOC (which is probably more useful \
than the map, but we have a need for pretty pictures as well ☺).

Thanks in advance for any feedback and advice!

Best regards
 
Giles Coochey

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
Nagios-users@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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
Nagios-users@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


[prev in list] [next in list] [prev in thread] [next in thread]