|
HTML rendering created 2025-09-06 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|
|
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | FILES | PCP ENVIRONMENT | DEBUGGING OPTIONS | SEE ALSO | COLOPHON |
|
|
|
PMLOGPUSH(1) General Commands Manual PMLOGPUSH(1)
pmlogpush - push an archive to a remote pmproxy server
pmlogpush [-vV?] [-D debug] [-h host] [-p port] [-s unix] [-Z
timezone] archive
pmlogpush sends the contents of a Performance Co-Pilot (PCP)
archive to a HTTP server (typically to a remote pmproxy(1) daemon)
using the logger API subset within the PMWEBAPI(5). The archive
must have been previously created using pmlogger(1).
This archive should be complete and finished (not actively being
written to). Comparable functionality is available directly from
pmlogger using the -R option, for pushing archives remotely while
they are actively being written.
The available command line options are:
-h hostname, --host=hostname
The hostname for the remote pmproxy server to receive the
given PCP archive.
-p port, --port=port
Internet socket port number where the remote pmproxy server
is listening, waiting to receive the given PCP archive. The
default port is 44322.
-s path, --unix=path
Unix domain socket path where a local pmproxy server is
listening (locally), waiting to receive the given PCP
archive.
-v, --verbose
Increase the diagnostic information reported as pmlogpush
runs.
-?, --help
Display usage message and exit.
-V, --version
Display version number and exit.
$PCP_LOG_DIR/pmproxy/<hostname>
Default directory for pushed PCP archives created (remotely)
by the receving pmproxy server. The hostname is extracted
from the given archive, as is the recording start time -
together these properties are used to name the pushed archive
on the receiving end (i.e. by the pmproxy server).
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).
The -D or --debug option enables the output of additional
diagnostics on stderr to help triage problems, although the
information is sometimes cryptic and primarily intended to provide
guidance for developers rather end-users. debug is a comma
separated list of debugging options; use pmdbg(1) with the -l
option to obtain a list of the available debugging options and
their meaning. The http debugging option is of particular
interest for this utility.
PCPIntro(1), pmlogger(1), pmproxy(1), PMWEBAPI(3), pcp.conf(5) and
pcp.env(5).
This page is part of the PCP (Performance Co-Pilot) project.
Information about the project can be found at
⟨http://www.pcp.io/⟩. If you have a bug report for this manual
page, send it to [email protected]. This page was obtained from the
project's upstream Git repository
⟨https://github.com/performancecopilot/pcp.git⟩ on 2025-08-11.
(At that time, the date of the most recent commit that was found
in the repository was 2025-08-11.) If you discover any rendering
problems in this HTML version of the page, or you believe there is
a better or more up-to-date source for the page, or you have
corrections or improvements to the information in this COLOPHON
(which is not part of the original manual page), send a mail to
[email protected]
Performance Co-Pilot PCP PMLOGPUSH(1)
Pages that refer to this page: pmwebapi(3)
|
HTML rendering created 2025-09-06 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|