From 4f45a5dc17423c04b52c4577dc6848beabb42792 Mon Sep 17 00:00:00 2001 From: William Cohen Date: Mon, 2 Mar 2026 16:20:58 -0500 Subject: [PATCH] docs: Eliminate some unsatisfied references --- docs/HowTos/scaling/index.rst | 6 +++--- docs/QG/QuickGuides.rst | 10 ++++------ 2 files changed, 7 insertions(+), 9 deletions(-) diff --git a/docs/HowTos/scaling/index.rst b/docs/HowTos/scaling/index.rst index 5ee1a9cb5da..841326df9d1 100644 --- a/docs/HowTos/scaling/index.rst +++ b/docs/HowTos/scaling/index.rst @@ -144,7 +144,7 @@ Results and Analysis Centralized logging (pmlogger farm) ----------------------------------- -The following results were gathered on a :ref:`pmlogger farm` deployment, +The following results were gathered on a :ref:`pmlogger farm` deployment, with a default **pcp-zeroconf 5.3.2** installation (version 5.3.1-3 on RHEL), where each remote host is an identical container instance running `pmcd(1)`_ on a server with 64 CPU cores, 376 GB RAM and 1 disk attached (as mentioned above, 64 CPUs increases per-CPU metric volume). The key server is co-located on the same host as pmlogger and pmproxy, and ``proc`` metrics of remote nodes are *not* included. @@ -184,8 +184,8 @@ For further troubleshooting, please see the `High memory usage`_ section in the Federated setup (multiple pmlogger farms) ----------------------------------------- -The following results were observed with a :ref:`federated setup` -consisting of three :ref:`pmlogger farms`, where each pmlogger farm +The following results were observed with a :ref:`federated setup` +consisting of three :ref:`pmlogger farms`, where each pmlogger farm was monitoring 100 remote hosts, i.e. 300 hosts in total. The setup of the pmlogger farms was identical to the configuration above (60s logging interval), except that the key servers were operating in cluster mode. diff --git a/docs/QG/QuickGuides.rst b/docs/QG/QuickGuides.rst index 153c3fb3f0e..f4af80c0bce 100644 --- a/docs/QG/QuickGuides.rst +++ b/docs/QG/QuickGuides.rst @@ -43,15 +43,13 @@ This guide contains the following topics: 15. :ref:`Establishing Secure Connections`, covers setting up secure connections between PCP collector and monitor components. Also, how network connections can be made secure against eavesdropping, data tampering and man-in-the-middle class attacks. -16. :ref:`Establishing Secure Client Connections`, covers setting up secure connections between PCP collector and monitor components and discuss setting up certificates on both the collector and monitor hosts. +16. :ref:`Setup Authenticated Connections`, covers setting up authenticated connections between PCP collector and monitor components. -17. :ref:`Setup Authenticated Connections`, covers setting up authenticated connections between PCP collector and monitor components. +17. :ref:`Importing data and creating PCP archives`, describes an alternative method of importing performance data into PCP by creating PCP archives from files or data streams that have no knowledge of PCP. -18. :ref:`Importing data and creating PCP archives`, describes an alternative method of importing performance data into PCP by creating PCP archives from files or data streams that have no knowledge of PCP. +18. :ref:`Using 3D views`, covers performance visualisation with *pmview*. -19. :ref:`Using 3D views`, covers performance visualisation with *pmview*. - -20. :ref:`Compare Archives and Report Significant Differences`, introduces the *pmdiff* tool that compares the average values for every metric in a given time window, for changes that are likely to be of interest when searching for performance regressions. +19. :ref:`Compare Archives and Report Significant Differences`, introduces the *pmdiff* tool that compares the average values for every metric in a given time window, for changes that are likely to be of interest when searching for performance regressions. Audience for This Guide ************************