Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

logimport(3) [centos man page]

LOGIMPORT(3)						     Library Functions Manual						      LOGIMPORT(3)

NAME
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)

Check Out this Related Man Page

PMLOGCHECK(1)						      General Commands Manual						     PMLOGCHECK(1)

NAME
pmlogcheck - checks for invalid data in a PCP archive SYNOPSIS
pmlogcheck [-lz] [-n pmnsfile] [-S start] [-T finish] [-Z timezone] archive DESCRIPTION
pmlogcheck prints information about the nature of any invalid data which it detects in a PCP archive. Of particular interest are wrapped values for metrics which are expected to have monotonically increasing values. The archive has the base name archive and must have been previously created using pmlogger(1). Normally pmlogcheck operates on the default Performance Metrics Namespace (pmns(5)), however if the -n option is specified an alternative namespace is loaded from the file pmnsfile. The command line options -S and -T can be used to specify a time window over which metrics should be summarized. These options are common to many Performance Co-Pilot tools and are fully described in PCPIntro(1). The -l option prints the archive label, showing the log format version, the time and date for the start and (current) end of the archive, and the host from which the performance metrics values were collected. By default, pmlogcheck reports the time of day according to the local timezone on the system where pmlogcheck is run. The -Z option changes the timezone to timezone in the format of the environment variable TZ as described in environ(5). The -z option changes the time- zone to the local timezone at the host that is the source of the performance metrics, as specified in the label record of the archive log. OUTPUT FORMAT
For each metric having ``counter'' semantics (i.e. the metric is expected to increase monotonically) which has been detected as having wrapped at some point in the archive, pmlogcheck produces output describing the metric name (with instance identifiers where appropriate), the internal storage type for the metric, the value of the metric before the counter wrap (with its associated timestamp), and the value of the metric after the wrap (also with a timestamp). pmlogcheck produces two different timestamp formats, depending on the interval over which it is run. For an interval greater than 24 hours, the date is displayed in addition to the time at which the counter wrap occurred. If the extent of the data being checked is less than 24 hours, a more precise format is used (time is displayed with millisecond precision, but without the date). FILES
$PCP_VAR_DIR/pmns/* default PMNS specification files $PCP_LOG_DIR/pmlogger/hostname default directory for PCP archives containing performance data collected from the host hostname. PCP ENVIRONMENT
Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. On each installation, the file /etc/pcp.conf contains the local values for these variables. The $PCP_CONF variable may be used to specify an alternative configura- tion file, as described in pcp.conf(5). SEE ALSO
PCPIntro(1), pmdumplog(1), pmlogextract(1), pmlogger(1), pmlogmerge(1), pmlogsummary(1), pmval(1), pcp.conf(5), pcp.env(5) and pmns(5). DIAGNOSTICS
All are generated on standard error and are intended to be self- explanatory. Performance Co-Pilot PCP PMLOGCHECK(1)
Man Page

Featured Tech Videos