The set of instances for performance metrics returned from a
pmFetch(3) call may be filtered or restricted using an instance
profile. There is one instance profile for each context the
application creates at the Performance Metrics Application
Programming Interface (PMAPI(3)), and each instance profile may
include instances from one or more instance domains (see
pmAddProfile may be used to add new instance specifications to the
instance profile of the current PMAPI context.
In the simplest variant, the list of instances identified by the
instlist argument for the indom instance domain are added to the
instance profile. The list of instance identifiers contains numinst
The indom value would normally be extracted from a call to
pmLookupDesc(3) for a particular performance metric, and the
instances in instlist would typically be determined by calls to
pmGetInDom(3) or pmLookupInDom(3).
To select all instances in all instance domains, use
pmAddProfile(PM_INDOM_NULL, 0, (int *)0)
This is the only case where indom may be equal to PM_INDOM_NULL. If
numinst is zero, or instlist is NULL, then all instances in indom are
It is possible to add non-existent instance domains and non-existent
instances to an instance profile. None of the routines that use the
instance profile will ever issue an error if you do this. The cost
of checking, when checking is possible, outweighs any benefits.
This page is part of the PCP (Performance Co-Pilot) project.
Information about the project can be found at ⟨http://www.pcp.io/⟩.
If you have a bug report for this manual page, send it to
firstname.lastname@example.org. This page was obtained from the project's upstream
Git repository ⟨git://git.pcp.io/pcp⟩ on 2017-03-13. If you discover
any rendering problems in this HTML version of the page, or you
believe there is a better or more up-to-date source for the page, or
you have corrections or improvements to the information in this
COLOPHON (which is not part of the original manual page), send a mail
Performance Co-Pilot PCP PMADDPROFILE(3)