Extended Service Information

[kevin]

Jeramy Eling wrote:
> Hi All,
> 
> I am trying, with very little success to get the extended service information to work in Nagios. I have spent the last few days trying to add the details to just one service, and no matter what I seem to do I just cannot get it to display. I have put my sample file below that I am working with:-
> 
> define serviceextinfo{
> 	host_name		adslfirewall
> 	service_description	PING
> 	notes_url		http://nagios/test2.html
> 	icon_image		win40.gif
> 	icon_image_alt		ADSL PING
> 	}
> 
> Can anyone give me any hints/tips on how I can get this working, I have read the documentation over and over and checked out the mailing-list but to no avail, I am using Nagios 1.2 on RedHat 9.0.
> 
> Thanks in advance
> 
> Jez
> 
The serviceextinfo that the check_traffic program made for me looks like 
this.
define serviceextinfo{
       host_name               storage4
       service_description     netapp
       notes_url    /nagios/cgi-bin/storage4_netapp.cgi
       icon_image              traffic-icon.jpg
       icon_image_alt          View graphs
}
So I would try changing the notes_url.  Also, for the icon to work it 
should be located in  /nagios/share/images/logos/
You should also check the nagios.cfg file to make sure that the 
serviceextinfo file is being loaded as a config file.  There should be a 
line that looks like this.
cfg_file=/usr/local/nagios/etc/serviceextinfo.cfg
After all that you should be able to restart nagios and see your note.

Kevin




-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
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