Hi,
On 2015-04-20 12:27, Marko Myllynen wrote:
>
> One mostly cosmetic thing I noticed with Perl PCP::PMDA is that while
> proc.psinfo maps instance numbers to PIDs (e.g. a process with PID
> 21641 is listed as 'inst [21641 or "021641 zsh"]'), with PCP::PMDA
> instance domain numbers are starting from 0 and can't be affected.
> Not sure does that actually matter in practice at all but if
> there's a trick to follow the proc.psinfo convention I could use it.
actually this might not be entirely cosmetic after all. I'm using
pidstat.threads as an example below but this looks to be generally
applicable usability issue as well.
When listing a metric from an archive with something like "pmval -t 1m
-f 3 -S @13:20 -T @13:30 -a 20150421.11.06 pidstat.threads" I see all
the instances reported, for example there could be "11173 java", "11188
java", and "13211 java" in the archive. But to list only one of them
seems tricky, one first needs to guess or loop over the archive to find
the instance ID (an integer) for the instance as it is not the PID and
-i "11173 java" won't work. In an archive I tested with, the instance
IDs were 974, 1021, and 1153 (as I've had pidstat PMDA running here for
several days already) so it's something that one needs to script around.
So it's a usability issue that can be dealt with on the command line but
if there would be a Web UI front-end in play I'm not sure how to guess
the instance IDs in that case.
Perhaps ideally with PCP::PMDA the instance ID could be set or -i would
accept the form "11173 java" (if unique). Do you see other alternatives
or should I perhaps file an RFE?
Thanks,
--
Marko Myllynen
|