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

NAME

6       ganglia2pcp - import ganglia data and create a PCP archive
7

SYNOPSIS

9       ganglia2pcp  [-d outdir] [-e end] [-f outfile] [-h hostname] [-s start]
10       [-Z timezone] input_dir
11

DESCRIPTION

13       ganglia2pcp is intended to read a set of ganglia files  stored  in  the
14       rrd format and translate them into a Performance Co-Pilot (PCP) archive
15       with the basename outfile.
16
17       The intent of this converter is to take all of the rrd files  found  in
18       the  input_dir  and generate a single pcp archive file.  The mapping of
19       ganglia metrics to pcp metrics is defined internally.
20
21       The resultant PCP achive may be used with all the PCP client  tools  to
22       graph  subsets of the data using pmchart(1), perform data reduction and
23       reporting, filter with the PCP inference engine pmie(1), etc.
24
25       A series of physical files will be created  with  the  prefix  outfile.
26       These  are outfile.0 (the performance data), outfile.meta (the metadata
27       that describes the performance  data)  and  outfile.index  (a  temporal
28       index  to improve efficiency of replay operations for the archive).  If
29       any of these files exists already, then sar2pcp will not overwrite them
30       and will exit with an error message of the form
31
32       __pmLogNewFile: ``blah.0'' already exists, not over-written
33
34       ganglia2pcp  is a Perl script that uses the PCP::LogImport Perl wrapper
35       around the PCP libpcp_import library, and as such could be used  as  an
36       example  to develop new tools to import other types of performance data
37       and create PCP archives.  The RRDs Perl wrapper is used  to  parse  the
38       raw rrd format files.
39

OPTIONS

41       The available command line options are:
42
43       -d outdir
44            The  outdir  argument specifies a output to write to.  The default
45            is the current directory.
46
47       -e end
48            The end argument specifies a end time in a  format  understood  by
49            str2time.  The default start time is current time.
50
51       -f outfile
52            The  outfile  argument  specifies a output file name.  The default
53            name is in the standard pmlogger format based on the  start  time,
54            e.g., 20150201.00.10.
55
56       -h hostname
57            The  hostname  argument  specifies  a hostname to write to the ar‐
58            chive.  The default is taken from the directory name that the  rrd
59            files reside in.
60
61       -s start
62            The  start  argument specifies a start time in a format understood
63            by str2time.  The default start time is 24 prior to current time.
64
65       -Z timezone
66            The timezone argument sets the source timezone in the PCP  archive
67            (the  default  is  to  use the local timezone).  The timezone must
68            have the format +HHMM (for hours and minutes East of UTC) or -HHMM
69            (for  hours  and  minutes West of UTC) or UTC.  Note in particular
70            that neither the zoneinfo (aka Olson) format,  e.g.  Europe/Paris,
71            nor  the  Posix TZ format, e.g.  EST+5 is allowed.  Example: time‐
72            zone=``+1100''.
73

PCP ENVIRONMENT

75       Environment variables with the prefix PCP_ are used to parameterize the
76       file  and  directory names used by PCP.  On each installation, the file
77       /etc/pcp.conf contains the  local  values  for  these  variables.   The
78       $PCP_CONF  variable may be used to specify an alternative configuration
79       file, as described in pcp.conf(5).
80

SEE ALSO

82       pmie(1),  pmchart(1),  pmlogger(1),  pmlogextract(1),  pmlogsummary(1),
83       Date::Parse(3pm), Date::Format(3pm), PCP::LogImport(3pm), RRDs(3pm) and
84       LOGIMPORT(3).
85
86
87
88Performance Co-Pilot                  PCP                       GANGLIA2PCP(1)
Impressum