On Mon, Nov 14, 2005 at 01:30:35PM +0300, Olleg Samoylov wrote: > Of cause, anyone need send perfdata to another program, to get rrd graphs. > There are two way to make this. Use service_perfdata_command. Or write > perfdata to named pipe and make parser read from it. > The second prefered, IMHO, because launch program, especially perl or awk > script > give heavy load. > There is not official perf parser. Some parsers need to be launched other > can read from named pipe.
while i think your suggestion is more efficient (and lower-load in
some situations), i think the default-perfdata approach is the
most generally compatible. if you have a parser that can read from
a named pipe, you could always make your service-perfdata command
"cat >> pipe"
which would minimize the load (not as good as it could be, but really
not that bad either). i guess you might need a little more than
that to make sure there aren't any race conditions, but we're
still talking about a relatively small overhead for most installations.
however, if we were to go the other way with file-perfdata, there
would be no way to execute the external programs, so i chose with
features and compatibility over pure efficiency.
> Nagios 2.x support write to file and command. May be better instead of
> deside what's better, file or command, make package for nagious 2.x? :)
this is of course a good point...
sean
--
signature.asc
Description: Digital signature
