pcp::logimport(3) [centos man page]

LogImport(3)						User Contributed Perl Documentation					      LogImport(3)

NAME

       PCP::LogImport - Perl module for importing performance data to create a Performance Co-Pilot archive

SYNOPSIS

	 use PCP::LogImport;

DESCRIPTION

       The PCP::LogImport module contains the language bindings for building Perl applications that import performance data from a file or real-
       time source and create a Performance Co-Pilot (PCP) archive suitable for use with the PCP tools.

       The routines in this module provide wrappers around the libpcp_import library.

SEE ALSO

       pmiAddInstance(3), pmiAddMetric(3), pmiEnd(3), pmiErrStr(3), pmiGetHandle(3), pmiPutResult(3), pmiPutValue(3), pmiPutValueHandle(3),
       pmiStart(3), pmiSetHostname(3), pmiSetTimezone(3), pmiUnits(3), pmiUseContext(3) and pmiWrite(3).

       The PCP mailing list pcp@oss.sgi.com can be used for questions about this module.

       Further details can be found at http://oss.sgi.com/projects/pcp

AUTHOR

       Ken McDonell, <kenj@internode.on.net>

       Copyright (C) 2010 by Ken McDonell.

       This library is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License, version 2 (see
       the "COPYING" file in the PCP source tree for further details).

perl v5.16.3							    2013-12-05							      LogImport(3)

PMIADDINSTANCE(3)					     Library Functions Manual						 PMIADDINSTANCE(3)

NAME

       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)