Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pmistart(3) [centos man page]

PMISTART(3)						     Library Functions Manual						       PMISTART(3)

pmiStart - establish a new LOGIMPORT context C SYNOPSIS
#include <pcp/pmapi.h> #include <pcp/impl.h> #include <pcp/import.h> int pmiStart(const char *archive, int inherit); cc ... -lpcp_import -lpcp Perl SYNOPSIS use PCP::LogImport; pmiStart($archive, $inherit); DESCRIPTION
As part of the Performance Co-Pilot Log Import API (see LOGIMPORT(3)), pmiStart creates a new context. Each context maintains the follow- ing state and metadata: o The base name (archive) for the physical files that constitute the output PCP archive. o The source hostname for the data that will be written to the PCP archive. Defaults to the hostname of the localhost, but can be set using pmiSetHostname(3). o The source timezone for the PCP archive. Defaults to the timezone of the localhost, but can be set using pmiSetTimezone(3). o Metrics and instance domains, as defined by pmiAddMetric(3). o Instances for each instance domain, as defined by pmiAddInstance(3). o Handles as defined by pmiGetHandle(3). Each handle is a metric-instance pair, and each metric-instance pair may have an associated value in each record written to the output PCP archive. o An optional set of data values for one or more metric-instance pairs (ready for the next record to be written to the output PCP archive) as defined by calls to pmPutValue(3) or pmPutValuehandle(3). If inherit is true, then the new context will inherit any and all metadata (metrics, instance domains, instances and handles) from the cur- rent context, otherwise the new context is created with no metadata. The basename for the output PCP archive, the source hostname, the source timezone and any data values from the current context are not inherited. If this is the first call to pmiStart the metadata will be empty independent of the value of inherit. Since no physical files for the output PCP archive will be created until the first call to pmiWrite(3) or pmiPutRecord(3), archive could be NULL to create a convenience context that is populated with metadata to be inherited by subsequent contexts. The return value is a context identifier that could be used in a subsequent call to pmUseContext(3) and the new context becomes the current context which persists for all subsequent calls up to either another pmiStart call or a call to pmiUseContext(3) or a call to pmiEnd(3). DIAGNOSTICS
It is an error if the physical files archive.0 and/or archive.index and/or archive.meta already exist, but this is not discovered until the first attempt is made to output some data by calling pmiWrite(3) or pmiPutRecord(3), so pmiStart always returns a positive context identi- fier. SEE ALSO
LOGIMPORT(3), pmiAddInstance(3), pmiAddMetric(3), pmiEnd(3), pmiErrStr(3), pmiGetHandle(3), pmiPutResult(3), pmiPutValue(3), pmiPutValue- Handle(3), pmiSetHostname(3), pmiSetTimezone(3), pmiUseContext(3) and pmiWrite(3). Performance Co-Pilot PMISTART(3)

Check Out this Related Man Page

PMIADDINSTANCE(3)					     Library Functions Manual						 PMIADDINSTANCE(3)

pmiAddInstance - add an element to an instance domain in a LOGIMPORT context C SYNOPSIS
#include <pcp/pmapi.h> #include <pcp/impl.h> #include <pcp/import.h> int pmiAddInstance(pmInDom indom, const char *instance, int inst); cc ... -lpcp_import -lpcp Perl SYNOPSIS use PCP::LogImport; pmiAddInstance($indom, $instance, $inst); DESCRIPTION
As part of the Performance Co-Pilot Log Import API (see LOGIMPORT(3)), pmiAddInstance adds a new element to the instance domain identified by indom. indom would normally be constructed using the pmInDom_build macro, e.g. pmInDom_build(PMI_DOMAIN,0) for the first instance domain in the Performance Metrics Domain PMI_DOMAIN (which is the default for all meta data created by the LOGIMPORT library). The new instance must have both an external name (instance) and an internal instance identifier (inst) that is unique across all instances in the indom instance domain. There is a special ``uniqueness rule'' for instance that is imposed by pmLookupInDom(3), namely that the external instance name must be unique in the leading non-space characters, e.g. the instance names ``foo'' and ``foo bar'' are considered the same by this rule and not allowed in the same instance domain, but ``foo'' and ``foobar'' would be allowed. Once defined, the external instance name can be used in calls to pmiGetHandle(3) and/or pmiPutValue(3) with the name of a metric defined over the same instance domain. DIAGNOSTICS
pmiAddInstance returns zero on success else a negative value that can be turned into an error message by calling pmiErrStr(3). SEE ALSO
LOGIMPORT(3), pmiAddMetric(3), pmiErrStr(3), pmiGetHandle(3), pmiPutValue(3) and pmLookupInDom(3). Performance Co-Pilot PMIADDINSTANCE(3)
Man Page

Featured Tech Videos