Hi -
aurelien.gonnay wrote:
> [...]
> My use case is fairly simple:
> [...]
> How can I instruct the local pmda proc to only watch that set of pids ?
The architected way would be to have your pcp client restrict the
instance domain for the proc. metrics via pmAddProfile etc. if in the
PMAPI, or via appropriate command line options if using CLI tools.
IOW, the pcp client would only ask for info on those processes,
therefore return only that data, which then you may log at whatever
rate you like. Note that this selection of instances ("instance
profile") is **per-client** rather than per-server configuration.
(In practice, there have been bugs in some pmdas in ignoring the
instance profile, and loading ("refreshing") unsolicited data about
other processes. That cost pmcd server-side time and sometimes led to
timeouts. Not sure whether these have all been fixed.)
A superblunt way, if applicable, could be to configure the proc pmda
to run under a userid that matches the one used by the interesting
processes on your machines. (Add a -U $USER option into
/etc/pcp/pmcd/pmcd.conf at the pmdaproc line.) Then the proc pmda
wouldn't be able to gather info about other processes in the first
place, so you wouldn't have to muck with instance domains.
- FChE
|