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

PMCONNECTLOGGER(3)					     Library Functions Manual						PMCONNECTLOGGER(3)

NAME

       __pmConnectLogger - connect to a performance metrics logger control port

C SYNOPSIS

       #include <pcp/pmapi.h>
       #include <pcp/impl.h>

       int __pmConnectLogger(const char *hostname, int pid);

       cc ... -lpcp

DESCRIPTION

       Each  instance  of  the	Performance  Co-Pilot  (PCP) archive logger program pmlogger(1) supports a control port on which __pmControlLog(3)
       requests are received, and responses sent.  Optionally, the pmlogger(1) instance may be designated the ``primary'' logger.

       __pmConnectLogger may be used to establish a control port connection to the pmlogger(1) instance identified by process id pid on  the  host
       hostname.

       One  special  case  is supported; for the reserved pid value of PM_LOG_CONTROL_PORT the requested connection is to the control port for the
       ``primary'' logger, whatever its process id might be.

       On success, __pmConnectLogger returns a non-negative integer, that is a file descriptor that may be used in subsequent  communication  with
       the pmlogger(1) instance, e.g. for __pmControlLog(3).

       As the control port to pmlogger(1) is not mulitplexed, applications using __pmConnectLogger should use close(2) to terminate the connection
       to pmlogger(1) as soon as they have finished communicating.

       If the application connects, and the pmlogger(1) instance subsequently terminates, e.g. because the associated pmcd(1) instance	is  termi-
       nated,  the  application  will have to explicitly re-establish connection to a re-started pmlogger(1) instance by calling __pmConnectLogger
       again.

SEE ALSO

       pmcd(1), pmlc(1), pmlogger(1), PMAPI(3) and __pmControlLog(3).

DIAGNOSTICS

       PM_ERR_PERMISSION
	      no permission to connect to the specified pmlogger(1) instance

       -ECONNREFUSED
	      the designated pmlogger(1) instance does not exist

       -EEADDRINUSE
	      the requested control port is already in use

Performance Co-Pilot							PCP							PMCONNECTLOGGER(3)

Linux and UNIX Man Pages

logimport(3) [centos man page]

Check Out this Related Man Page