Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pmiputvalue(3) [centos man page]

PMIPUTVALUE(3)						     Library Functions Manual						    PMIPUTVALUE(3)

pmiPutValue - add a value for a metric-instance pair C SYNOPSIS
#include <pcp/pmapi.h> #include <pcp/impl.h> #include <pcp/import.h> int pmiPutValue(const char *name, const char *instance, const char *value); cc ... -lpcp_import -lpcp Perl SYNOPSIS use PCP::LogImport; pmiPutValue($name, $instance, $value); DESCRIPTION
As part of the Performance Co-Pilot Log Import API (see LOGIMPORT(3)), pmiPutValue adds a single value to the current output record for a given metric and instance. The metric's name should match one defined earlier in a call to pmiAddMetric(3). For singular metrics (those defined with an instance domain of PM_INDOM_NULL), the instance should be NULL or an empty string, otherwise instance should match the name of an instance defined earlier in a call to pmiAddInstance(3) for the metric's instance domain. The value should be in a format consistent with the metric's type as defined in the call to pmiAddMetric(3). No data will be written until pmiWrite(3) is called, so multiple calls to pmiPutValue or pmiPutValueHandle(3) are typically used to accumu- late data values for several metric-instance pairs before calling pmiWrite(3). DIAGNOSTICS
pmiPutValue returns zero on success else a negative value that can be turned into an error message by calling pmiErrStr(3). SEE ALSO
LOGIMPORT(3), pmiAddInstance(3), pmiAddMetric(3), pmiErrStr(3), pmiPutResult(3), pmiPutValueHandle(3) and pmiWrite(3). Performance Co-Pilot PMIPUTVALUE(3)

Check Out this Related Man Page

LOGIMPORT(3)						     Library Functions Manual						      LOGIMPORT(3)

LOGIMPORT - introduction to the library for importing data and creating a PCP archive C SYNOPSIS
#include <pcp/pmapi.h> #include <pcp/impl.h> #include <pcp/import.h> cc ... -lpcp_import -lpcp Perl SYNOPSIS use PCP::LogImport; DESCRIPTION
The Performance Co-Pilot Log Import (LOGIMPORT) API is a library (and Perl wrapper) that supports the creation of PCP archives from exter- nal sources of performance data, either in the form of historical logs and spreadsheets or from real-time sources that are not integrated as a Performance Metrics Domain Agent (PMDA) under the control of pmcd(1). The typical usage for LOGIMPORT would involve: o An initial call to pmiStart(3). o Optional calls to pmiSetHostname(3) and/or pmiSetTimezone(3) to set the hostname and timezone for the source of the performance data. o One or more calls to pmiAddMetric(3) to define performance metrics. o One or more calls to pmiAddInstance(3) to define instances associated with the metrics. o Optional calls to pmiGetHandle(3) to defined convenience handles for metric-instance pairs. o A main loop in which performance data is injested and for each sample time interval, the PCP archive record is constructed by calls to pmiPutValue(3) and/or pmiPutValueHandle(3), followed by a call to pmiWrite(3) to flush all data and any associated new metadata to the PCP archive. Alternatively, pmiPutResult(3) could be used to package and process all the data for one sample time interval. o Once the input source of data has been consumed, calling pmiEnd(3) to complete the PCP archive creation and close all open files. If new metrics and/or instances are discovered during the data injestion, these can be added by subsequent calls to pmiAddMetric(3) and/or pmiAddInstance(3), provided all the metrics and instances have been defined before a call to pmiGetHandle(3), pmiPutValue(3)or pmiPutRe- sult(3) that references those metrics and instances. SEE ALSO
pmcd(1), pmlogger(1), pmiGetHandle(3), pmiAddInstance(3), pmiAddMetric(3), pmiEnd(3), pmiErrStr(3), pmiPutResult(3), pmiPutValue(3), pmiPutValueHandle(3), pmiSetHostname(3), pmiSetTimezone(3), pmiStart(3) and pmiWrite(3). Performance Co-Pilot LOGIMPORT(3)
Man Page

Featured Tech Videos