Frank's correct. pmlc was conceived at the same time pmlogger was created
for just this purpose ... and the equally important case - after some
elapsed time, if we don't know what's going on, we're never going to find
out, so stop logging those additional metrics.
All of the plumbing already exists for both the turning on and turning off
to be driven by pmie (if the triggers to stop/start can be captured by pmie
rules). It is all a bit low-level, but has been made to work in the past
and will still work.
If you need any assistance putting this together, I can help if I know the
specific details.
> -----Original Message-----
> From: pcp-bounces@xxxxxxxxxxx [mailto:pcp-bounces@xxxxxxxxxxx] On
> Behalf Of Frank Ch. Eigler
> Sent: Saturday, 12 April 2014 5:04 AM
> To: Martins Innus
> Cc: PCP Mailing List
> Subject: Re: [pcp] signal pmlogger
>
>
> minnus wrote:
>
> > [...] I'm trying to find a way to send a signal to pmlogger to log
> > certain metrics immediately. [...]
>
> See the pmlc tool. It can direct a pmlogger instance to log new metrics
on
> demand. (One can imagine a future where this is automated via pmie or
> other ways.)
>
> - FChE
>
> _______________________________________________
> pcp mailing list
> pcp@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/pcp
|