PMDUMPLOG(1) | General Commands Manual | PMDUMPLOG(1) |
pmdumplog - dump internal details of a performance metrics archive log
pmdumplog [-adehilLmMrstxz] [-n
pmnsfile] [-S starttime] [-T endtime]
[-Z timezone] archive [metricname ...]
pmdumplog [-v file]
pmdumplog dumps assorted control, metadata, index and state information from the files of a Performance Co-Pilot (PCP) archive log. The archive log has the base name archive and must have been previously created using pmlogger(1).
Normally pmdumplog operates on the distributed Performance Metrics Name Space (PMNS), however if the -n option is specified an alternative local PMNS is loaded from the file pmnsfile.
If any metricname arguments appear, the report will be restricted to information relevant to the named performance metrics. If metricname is a non-leaf node in the namespace (see pmns(5)), then pmdumplog will recursively descend the archive's namespace and report on all leaf nodes.
The options control the specific information to be reported.
Metrics without an instance domain are reported as:
[timestamp] metric-id (metric-name): value1
value2
Metrics with an instance domain are reported as:
[timestamp] metric-id (metric-name):
inst [internal-id or "external-id"]
value1 value2
The timestamp is only reported for the first metric in a group of metrics sharing the same timestamp.
<mark> records are inserted into a PCP archive log by pmlogger(1), pmlogextract(1), and similar tools to indicate a temporal discontinuity in the time-series of metric values.
The integrity of the index will also be checked. If the index is found to be corrupted, the ``*.index'' file can be renamed or removed and the archive will still be accessible, however retrievals may take longer without the index. Note however that a corrupted temporal index is usually indicative of a deeper malaise that may infect all files in a PCP archive.
Use of -v precludes the use of all other options and arguments.
A second -x option will also report the timestamp as an offset from the start of the archive in units of seconds. This is useful in conjunction with debug diagnostics from the archive handling routines in libpcp.
By default, pmdumplog reports the time of day according to the local timezone on the system where pmdumplog is run. The -Z option changes the timezone to timezone in the format of the environment variable TZ as described in environ(7). The -z option changes the timezone 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.
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).
PCPIntro(1), pmlogcheck(1), pmlogger(1), pmlogger_check(1), pmlogger_daily(1), pmloglabel(1), pmlogextract(1), PMAPI(3), pmGetInDom(3), pmLookupDesc(3), pcp.conf(5), pcp.env(5) and pmns(5).
PCP | Performance Co-Pilot |