Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pmdastore(3) [centos man page]

PMDASTORE(3)						     Library Functions Manual						      PMDASTORE(3)

NAME
pmdaStore - store a value into a metric for a PMDA C SYNOPSIS
#include <pcp/pmapi.h> #include <pcp/impl.h> #include <pcp/pmda.h> int pmdaStore(pmResult *result, pmdaExt *pmda); cc ... -lpcp_pmda -lpcp DESCRIPTION
As part of the Performance Metrics Domain Agent (PMDA) API (see PMDA(3)), pmdaStore is the generic callback for storing a value into a met- ric. pmdaStore is usually a no-op as, by default, no metrics can be altered. Also, the implementation of a store callback which does per- mit metrics to be altered by pmstore(1) is very application dependent. DIAGNOSTICS
pmdaStore returns PM_ERR_PERMISSION to indicate that no metrics may be modified. CAVEAT
The PMDA must be using PMDA_PROTOCOL_2 or later, as specified in the call to pmdaDSO(3) or pmdaDaemon(3). SEE ALSO
pmstore(1), PMAPI(3), PMDA(3), pmdaDaemon(3), pmdaDSO(3) and pmStore(3). Performance Co-Pilot PCP PMDASTORE(3)

Check Out this Related Man Page

PMDAPROFILE(3)						     Library Functions Manual						    PMDAPROFILE(3)

NAME
pmdaProfile - update instance profile for PMDA in preparation for the next fetch from PMCD C SYNOPSIS
#include <pcp/pmapi.h> #include <pcp/impl.h> #include <pcp/pmda.h> int pmdaProfile(__pmProfile *prof, pmdaExt *pmda); cc ... -lpcp_pmda -lpcp DESCRIPTION
As part of the Performance Metrics Domain Agent (PMDA) API (see PMDA(3)), pmdaProfile is the default callback which handles the receipt of a __pmProfile from pmcd(1). A profile describes the instances that pmcd requires in the pmResult structure returned by the next fetch. pmdaProfile simply stores the new profile. CAVEAT
The PMDA must be using PMDA_PROTOCOL_2 or later, as specified in the call to pmdaDSO(3) or pmdaDaemon(3). SEE ALSO
PMAPI(3), PMDA(3), pmdaDaemon(3), pmdaDSO(3) and pmdaFetch(3). Performance Co-Pilot PCP PMDAPROFILE(3)
Man Page