matthias eble wrote:
>>> Maybe tuning config.cgi to accept host/service names/descriptions
>>> would
>>> be best. With a nice two column table, overview for single
>>> hosts/services would be better. The link could be added to the top
>>> left
>>> box.
>> I can't quite picture what you mean. Are you saying that on the /cgi-
>> bin/extinfo.cgi?type=1&host=hostname screen, a link is in the top left
>> box that is (say) "View Configuration Detail For This Host"?
> yup
>> This
>> would go to extinfo.cgi with a different type id (?) and then print
>> all configuration data, including parents, children, contacts and
>> contactgroups?
>
> I'd place the logic into config.cgi. That would (if supplied with a
> hostname or hostname+service_description argument) print a nice table
> including links to parents, contacts, check_command, interval,...
>
> Of course, with the current data structures looking up children will be
> painful in large installations.
>
Not necessarily. The object config parsing code is already riddled with
#ifdef NSCORE
do_stuff();
#elif defined(NSCGI)
do_other_stuff();
#endif
so we could potentially add this stuff to the CGI's. It's not my itch to
scratch, but I'll accept patches along those lines.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Register now for Nordic Meet on Nagios, June 3-4 in Stockholm
http://nordicmeetonnagios.op5.org/
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]