From: Yves M. <yme...@li...> - 2004-09-02 12:28:20
|
Partial anwser in what I feel concerned... :) Ben will probably answer the rest when he's less busy. [...] > - xpdfile* configuration in nagios did not work for me, but you should > note in README that it also works if you use > > host_perfdata_command=3Dprocess-host-perfdata > service_perfdata_command=3Dprocess-service-perfdata > > in nagios.cfg and > define command{ > command_name process-host-perfdata > command_line /usr/bin/printf "%b" > "$TIMET$\t$HOSTNAME$\t$OUTPUT$\t$PERFDATA$\n" >> > /usr/local/nagios/var/host-perfdata.out > } > define command{ > command_name process-service-perfdata > command_line /usr/bin/printf "%b" > "$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDAT= A$\n" >> > /usr/local/nagios/var/service-perfdata.out > } > > in misccommands.cfg I have some similar suggestion: In nagios.cfg: host_perfdata_command=3Dprocess-host-perfdata service_perfdata_command=3Dprocess-service-perfdata cfg_file=3D/some/path/perfparse.cfg In perfparse.cfg: exactly what you just wrote, but not in misccommands.cf= g. I think that it is better because that way, we can provide perfparse.cfg = ourself and only ask people to change those 3 lines. We can even put only cfg_file=3D/some/path/perfparse.cfg, ask to comment = the other perfdata commands in nagios.cfg, and provide perfparse.cfg with everythin= g. > Last: some notes: > > - Very cool feature. I want it! > - Why did you write it in C. Would'nt it be easier to use perl or php. > Probably the perfparse should remain in C for speed purposes, but the w= eb > frontend would be more flexible in php. perfparse and perfchart.png are in C for speed purposes. Yes, maybe perfg= raph.cgi can be written in php ? I agree with you, but who will do it ? Yves --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - GTKtalog - http://www.nongnu.org/gtktalog/ - |