pcp
[Top] [All Lists]

Re: New pmlognow utility

To: PCP <pcp@xxxxxxxxxxx>
Subject: Re: New pmlognow utility
From: Martins Innus <minnus@xxxxxxxxxxx>
Date: Mon, 17 Aug 2015 09:35:02 -0400
Cc: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <y0megj5bozh.fsf@xxxxxxxx>
References: <55CCF097.7070902@xxxxxxxxxxx> <y0megj5bozh.fsf@xxxxxxxx>
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
Frank,

On 8/14/15 4:21 PM, Frank Ch. Eigler wrote:
minnus wrote:

[...]
pmlognow -s -p job-1000-begin- -d /var/log/pcp/pmlogger/HOSTNAME -c
/etc/pcp/pmlogger/pmlogger-config.ubccr
[...]
(Assuming -h local: ?)

For now, yes, that was all we needed. But other functionality could be added later on.


Have you tried something like:

% echo 'log mandatory on once {foo.bar foo.baz}' | pmlc $PMLOGGER_PORT # or -P


Yeah, I think we discussed some possible options with you and Nathan last year. Since we wanted to have just one config file for our logging, it would have required some scripting anyway to start up another logger, parse our logger config, convert all the directives to "log once" and then feed that to pmlc, it seemed like I might as well just use the api directly. And we get something that we might have other uses for. I'm interested to see how Marko fleshes out the idea here:

https://bugzilla.redhat.com/show_bug.cgi?id=1242463

I think we would have a use case for doing a "log now" of a set of metrics defined by an alias for diagnosis of different classes of application that might be running.

Thanks

Martins

<Prev in Thread] Current Thread [Next in Thread>