pmwtf(1) [centos man page]

PMWTF(1)						      General Commands Manual							  PMWTF(1)

NAME

       pmwtf - compares archives and report significant differences

SYNOPSIS

       pmwtf  [-dz] [-p precision] [-q thres] [-S starttime] [-T endtime] [-B starttime] [-E endtime] [-x metric] [-X file] [-Z timezone] archive1
       [archive2]

DESCRIPTION

       pmwtf compares the average values for every metric in either one or two archives, in a given time window, for changes that are likely to be
       of interest when searching for performance regressions.

       The  archive log has the base name archive and must have been previously created using pmlogger(1).  The pmlogsummary(1) utility is used to
       obtain the average values used for comparison.

       There are two sorts of invocation of the tool: with either one or two archives.

       In the first case, the only sensible command line requires use of all four time window arguments.  These are specified using the same  time
       window  format described in PCPIntro(1), and are -S and -T for the start and end times of the first time window of interest in the archive,
       and -B and -E for the start and end times of the second time window of interest.

       In the second case, with two archives, the -B and -E options might be unnecessary.  This might be the case, for example, when comparing the
       same time window of two consecutive days (usually two separate archives), or a time window on the same day of different weeks.

       In either case, pmwtf produces a sorted summary of those metrics in the specified window whose values have deviated the most from a minimal
       threshold.  The level of deviation is calculated by dividing the average value of each metric in both logs, and	then  calculating  whether
       the  ratio falls outside of a range considered normal.  This ratio can be adjusted using the -q option, and by default it is 2 (i.e. report
       all metrics with average values that have more than doubled in the two time windows or more than halved in the two time windows).

       Should any metrics be present in one window but missing from the other, a diagnostic will be displayed listing each missing metric and  the
       archive from which it was missing.

       The  remaining options control the specific information to be reported.	Metrics with counter semantics are converted to rates before being
       evaluated.

       -p   Print all floating point numbers with precision digits after the decimal place.

       -x   Compare each metric in each archive in the time windows specified to a given egrep(1) pattern, excluding those  that  match  from  the
	    report output.

       -X   Allows a file to be specified which containing egrep(1) patterns which are applied to the metric names to optionally exclude some from
	    the report.

       -z   Use the local timezone from the given archives.

       -Z   Changes the timezone in the archive labels to timezone in the format of the environment variable TZ as described in environ(5).

FILES

       $PCP_LOG_DIR/pmlogger/hostname
		 Default directory for PCP archives containing performance metric values 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), pmlogger(1), pmlogsummary(1), egrep(1), pcp.conf(5) and pcp.env(5).

Performance Co-Pilot							PCP								  PMWTF(1)

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)

Linux and UNIX Man Pages

pmwtf(1) [centos man page]

Check Out this Related Man Page