NAME¶

pmnsmerge - merge multiple versions of a Performance Co-Pilot PMNS

SYNOPSIS¶

$PCP_BINADM_DIR/pmnsmerge[-adfxv] infile[...]outfile

DESCRIPTION¶

pmnsmergemerges multiple instances of aPerformance Metrics Name Space (PMNS),as used by the components of thePerformance Co-Pilot (PCP).

Eachinfileargument names a file that includes the root of a PMNS, of the form

root {


    /* arbitrary stuff */
}

The order in which theinfilefiles are processed is determined by the presence or absence ofembedded control lines of the form

#define _DATESTAMP YYYYMMDD

Files without a control line are processed first and in theorder they appear on the command line.The other files are then processed in order of ascending_DATESTAMP.

The-aoption suppresses the argument re-ordering and processes all filesin the order they appear on the command line.

The merging proceeds by matching names in PMNS, only thosenew names in each PMNS are considered, and these are added after any existing metrics with the longest possible matching prefix in their names. For example, merging these two input PMNS

root {                    root {


                              surprise  1:1:3


    mine       1:1:1          mine      1:1:1


    foo                       foo


                              yawn


    yours      1:1:2
}                         }
foo {                     foo {


    fumble     1:2:1


                              mumble    1:2:3


    stumble    1:2:2          stumble   1:2:2
}                         }


                          yawn {


                              sleepy    1:3:1


                          }

Produces the resulting PMNS inout.

root {


    mine      1:1:1


    foo


    yours     1:1:2


    surprise  1:1:3


    yawn
}
foo {


    fumble    1:2:1


    stumble   1:2:2


    mumble    1:2:3
}
yawn {


    sleepy    1:3:1
}

To avoid accidental over-writing of PMNS files,outfileis expected to not exist whenpmnsmergestarts.The-foption allows an existingoutfileto be unlinked (if possible) and truncated before writing starts.

Normallyduplicate names for the same Performance Metric Identifier (PMID) ina PMNS are allowed.The-doption is the default option and is included for backwards compatibility.The-xoption reverses the default andpmnsmergewill report an error and exit with a non-zero status if a duplicatename is found for a PMID in any of theinputPMNS files or in the mergedoutputPMNS.

The-voption produces one line of diagnostic output as eachinfileis processed.

Once all of the merging has been completed,pmnsmergewill attempt to loadthe resultant namespace usingpmLoadASCIINameSpace(3)- if this fails for any reason,outfilewill still be created, butpmnsmergewill report the problem and exit with non-zero status.

Usingpmnsmergewith a singleinputargument allows that PMNS file to be checked.In addition tosyntactic checking, specifying-xwill also enable a check for duplicate names for all PMIDs.

OPTIONS¶

The available command line options are:

-a

Process files in command line order.

-d, --dupok

Allow duplicate metric names per PMID.This is the default.

-f, --force

Overwrite output file if it already exists.

-v, --verbose

Verbose input processing.

-x, --nodups

Do not allow duplicate metric names per PMID.

-?, --help

Display usage message and exit.

CAVEATS¶

Once the writing of the newoutfilefile has begun, the signals SIGINT, SIGHUP and SIGTERM will be ignoredto protect the integrity of the new file.

PCPENVIRONMENT¶

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 configuration file, as described in pcp.conf(5).

SEEALSO¶

pmnsadd(1),pmnsdel(1),pmLoadASCIINameSpace(3),pcp.conf(5),pcp.env(5)andPMNS(5).