1PMDUMPLOG(1)                General Commands Manual               PMDUMPLOG(1)
2
3
4

NAME

6       pmdumplog - dump internal details of a performance metrics archive log
7

SYNOPSIS

9       pmdumplog [-adilLmMrstxz] [-n pmnsfile] [-S starttime] [-T endtime] [-Z
10       timezone] archive [metricname ...]
11       pmdumplog [-v file]
12

DESCRIPTION

14       pmdumplog dumps assorted control, metadata, index and state information
15       from  the  files  of a Performance Co-Pilot (PCP) archive log.  The ar‐
16       chive log has the base name archive and must have been previously  cre‐
17       ated using pmlogger(1).
18
19       Normally pmdumplog operates on the distributed Performance Metrics Name
20       Space (PMNS), however if the -n  option  is  specified  an  alternative
21       local PMNS is loaded from the file pmnsfile.
22
23       If  any  metricname  arguments appear, the report will be restricted to
24       information relevant to the named performance metrics.   If  metricname
25       is  a non-leaf node in the namespace (see pmns(5)), then pmdumplog will
26       recursively descend the archive's namespace  and  report  on  all  leaf
27       nodes.
28
29       The options control the specific information to be reported.
30
31       -a   Report everything, i.e. the flags -d, -i, -l, -m, -s and -t.
32
33       -d   Display  the  metadata and descriptions for those performance met‐
34            rics that appear at least once in the archive: see pmLookupDesc(3)
35            for more details on the metadata describing metrics.
36
37       -i   Display the instance domains, and any variations in their instance
38            members over the duration of the archive:  see  pmGetInDom(3)  for
39            more details on instance domains.
40
41       -l   Dump  the  archive label, showing the log format version, the time
42            and date for the start and (current) end of the archive,  and  the
43            host from which the performance metrics values were collected.
44
45       -L   Like -l, just a little more verbose.
46
47       -m   Print  the  values  for  the performance metrics from the archive.
48            This is the default display option.
49
50            Metrics without an instance domain are reported as:
51              [timestamp] metric-id (metric-name): value1 value2
52
53            Metrics with an instance domain are reported as:
54              [timestamp] metric-id (metric-name):
55                  inst [internal-id or "external-id"] value1 value2
56
57            The timestamp is only reported for the first metric in a group  of
58            metrics sharing the same timestamp.
59
60       -M   If  no  metricname  is  specified then <mark> records are reported
61            when they are found in the archive.  If metricname  arguments  are
62            specified,  then  <mark> records are not reported by default.  The
63            -M option forces <mark> records to be reported, even when  metric‐
64            name arguments are specified.
65
66       -r   Process  the  archive in reverse order, from most recent to oldest
67            recorded metric values.
68
69       -S   When using the -m option, the report will be restricted  to  those
70            records  logged at or after starttime.  Refer to PCPIntro(1) for a
71            complete description of the syntax for starttime.
72
73       -s   Report the size in bytes of each physical record in the archive.
74
75       -T   When using the -m option, the report will be restricted  to  those
76            records  logged  before or at endtime.  Refer to PCPIntro(1) for a
77            complete description of the syntax for endtime.
78
79       -t   Dump the temporal index that is used to provide accelerated access
80            to large archive files.
81
82            The  integrity of the index will also be checked.  If the index is
83            found to be corrupted, the ``*.index''  file  can  be  renamed  or
84            removed   and  the  archive  will  still  be  accessible,  however
85            retrievals may take longer without the index.  Note however that a
86            corrupted temporal index is usually indicative of a deeper malaise
87            that may infect all files in a PCP archive.
88
89       -v   Verbose mode.  Dump the records from a physical  archive  file  in
90            hexadecimal  format.   In  this  case file is the name of a single
91            file, usually a basename (as would otherwise appear as the archive
92            command line argument), concatenated with ``.'' followed by one of
93            meta (the metadata), index (the temporal index), or a  digit  (one
94            of the volumes of metric values).
95
96            Use of -v precludes the use of all other options and arguments.
97
98       -x   Extended  timestamp  reporting format that includes the day of the
99            week, day of  the  month,  month  and  year  in  addition  to  the
100            (default) hours, minutes and seconds time.  This is useful for ar‐
101            chives that span multiple days.
102
103            A second -x option will also report the  timestamp  as  an  offset
104            from the start of the archive in units of seconds.  This is useful
105            in conjunction with debug diagnostics from  the  archive  handling
106            routines in libpcp.
107
108       By  default,  pmdumplog  reports the time of day according to the local
109       timezone on the system where pmdumplog is run.  The -Z  option  changes
110       the  timezone  to timezone in the format of the environment variable TZ
111       as described in environ(7).  The -z option changes the timezone to  the
112       local  timezone  at the host that is the source of the performance met‐
113       rics, as specified in the label record of the archive log.
114

FILES

116       $PCP_VAR_DIR/pmns/*
117                 default local PMNS specification files
118       $PCP_LOG_DIR/pmlogger/hostname
119                 Default directory for  PCP  archives  containing  performance
120                 metric values collected from the host hostname.
121

PCP ENVIRONMENT

123       Environment variables with the prefix PCP_ are used to parameterize the
124       file and directory names used by PCP.  On each installation,  the  file
125       /etc/pcp.conf  contains  the  local  values  for  these variables.  The
126       $PCP_CONF variable may be used to specify an alternative  configuration
127       file, as described in pcp.conf(5).
128

SEE ALSO

130       PCPIntro(1),   pmlogcheck(1),  pmlogger(1),  pmlogger_check(1),  pmlog‐
131       ger_daily(1), pmloglabel(1), pmlogextract(1), PMAPI(3),  pmGetInDom(3),
132       pmLookupDesc(3), pcp.conf(5), pcp.env(5) and pmns(5).
133
134
135
136Performance Co-Pilot                  PCP                         PMDUMPLOG(1)
Impressum