That solves that problem then, thanks for the help. Trying to get out of the nagios way of thinking.
nick cluther wrote: > > > After reading the documents over and over again i am starting to get > > how zenoss works but one major thing i think i have missed is how > > nagios commands work in zenoss. > > > > I have added the nagios command to a template and the command line > > test works fine but! > > > > How do you get that nagios command to show up in the (OS) menu > > listing or somthing similar. > > > > If i added a nagios check check_http like the one in all the > > examples how to i check what the current status of that check is > > other than looking at the graph. > > > > The graph is the only place you'll see any visualization of the check > if it is returning an OK (0) exit code. Zenoss is an event based > system vs. Nagios which is a status based system. If your Nagios > plugin returns a warning or critical response it will become an event > in Nagios. > > We take a "tell me when something is wrong" approach rather than a > "tell me everything" approach. > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=12937#12937 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
