1PMLOGPASTE(1) General Commands Manual PMLOGPASTE(1)
2
3
4
6 pmlogpaste - paste text into a metric in a PCP archive
7
9 pmlogpaste [-?] [-f file] [-h hostname] [-m metric] [-o outfile] [-t
10 timezone] [-l label]
11
13 pmlogpaste takes input text from a file or the command line, and writes
14 it as a metric value in a new PCP archive. This metric value is times‐
15 tamped with the current time, and is stored as a string type metric.
16
17 The main purpose of this tool is to take captured output and preserve
18 this in a PCP archive. This allows, for example, the output of a
19 benchmark run to be stored along with performance metrics captured dur‐
20 ing that run, in a single archive. Archives can be merged using the
21 pmlogextract(1) utility.
22
23 pmlogpaste uses the LOGIMPORT(3) library interfaces internally, which
24 support the creation of archives from external sources of performance
25 data.
26
28 The available command line options are:
29
30 -h hostname, --hostname=hostname
31 source host name for a LOGIMPORT archive. The default value is
32 the local host name, or ``localhost'' if that cannot be
33 obtained.
34
35 -t timezone, --timezone=timezone
36 source timezone for a LOGIMPORT archive. The default value is
37 the local timezone.
38
39 -m metric, --metric=metric
40 metric name for a LOGIMPORT archive. The default metric name is
41 paste.value.
42
43 -f file, --file=file
44 file with input text to be archived, or ``-'' for standard
45 input.
46
47 -o outfile, --outfile=outfile
48 archive output file. The default archive name is paste.
49
50 -l label, --label=label
51 Add context labels to the generated archive. This option can be
52 presented multiple times to produce multiple labels in the ar‐
53 chive. The label should be in the form name:value.
54
55 -?, --help
56 Display usage message and exit.
57
59 All are generated on standard error and are intended to be self-
60 explanatory.
61
63 Environment variables with the prefix PCP_ are used to parameterize the
64 file and directory names used by PCP. On each installation, the file
65 /etc/pcp.conf contains the local values for these variables. The
66 $PCP_CONF variable may be used to specify an alternative configuration
67 file, as described in pcp.conf(5).
68
70 PCPIntro(1), pmcd(1), pmlogextract(1) and LOGIMPORT(3).
71
72
73
74Performance Co-Pilot PCP PMLOGPASTE(1)