Hi Nathan et al.
Thought I'd add my 2 cents as someone on the receiving end of
configuring pmlogger.
Auto-discovery via Avahi is good idea but does assume a certain network
configuration. Multicast must be allowed in the network and for
inter-vlan discovery, multicast routing is also required (something
seldom configured in the enterprise).
Also, most cloud provides (including AWS/EC2) do not permit multicast
in it's entirety.
I (personally) like the idea that clients can inform a pmlogger that
they want to be logged via a well known hostname or IP address that the
administrator knows. DNS (and the search path) could do the
heavy-lifting to find the right pmlogger host to talk to.
Anyway, some food for thought. Cheers!
Ryan
On Mon, 1 Jul 2013 06:16:02 -0400 (EDT), Nathan Scott
<nathans@xxxxxxxxxx> wrote:
----- Original Message -----
AIUI, we need something running all the time (daemon) that is able
to catch
these Avahi events as they happen, indicating a pmcd has been
detected on
the network that is available for logging (or inference).
Above we have "pmlogger or pmlogconf or whatnot" suggested - I think
it has
to be the latter (whatnot). With the current model, pmlogger is
designed to
record an archive for one host only - this requires something to
start/stop
Hmm, "this" is ambiguous here => I meant "this funky Avahi
auto-logging stuff"
and not "this current pmlogger model".
logging arbitrary hosts as they come/go on the network. pmlogconf
today is
cheers.
--
Nathan
_______________________________________________
pcp mailing list
pcp@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/pcp
|