On 11/21/05, Max <[EMAIL PROTECTED]> wrote: > I have mrtg setup on my Nagios box to link to whatever graph I want > specified in my serviceextinfo.cfg. I looked at the documentation but > couldn't find the answer to my question. > > I'm thinking it's not possible, but I figured I would ask anyways. First > an example of my serviceextinfo.cfg: > > define serviceextinfo{ > host_name my-host-example > service_description DISKS > notes_url http://link-to-my-graph > icon_image graph.gif > icon_image_alt View graphs > } > > Can I specify more than one pointer from within a container? For > example, I have disks being monitored and I have say three graphs being > generated from my mrtg configurations. With the current setup however I > can only make a direct link to one of those graphs with only one little > image showing up under that particular service. I would like to be able > to show three images on the service DISKS with a link to each > corresponding graph? > > If not no big deal, I can always just create a directory, point Apache > to it, and have my image link open to that directory, where you can > select the graph you want to look at. I was just trying to make it > "pretty" looking from the Nagios interface though. Thanks for any replies. >
Max, Not sure if this is possible, but it would be a nice addition. Id like to link to graphs and documentation. Addng a serviceextinfo definition for the service linking it to a wiki page seems a nice easy way to achieve although you can obviously create only one link per service. Ben ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28&alloc_id845&op=click _______________________________________________ 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