Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/HowTos/scaling/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ Results and Analysis
Centralized logging (pmlogger farm)
-----------------------------------

The following results were gathered on a :ref:`pmlogger farm<C. Centralized logging (pmlogger farm)>` deployment,
The following results were gathered on a :ref:`pmlogger farm<C.1 Centralized logging (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.
Expand Down Expand Up @@ -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<D. Federated setup (multiple pmlogger farms)>`
consisting of three :ref:`pmlogger farms<C. Centralized logging (pmlogger farm)>`, where each pmlogger farm
The following results were observed with a :ref:`federated setup<Federated setup (multiple pmlogger farms)>`
consisting of three :ref:`pmlogger farms<C.1 Centralized logging (pmlogger farm)>`, 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.

Expand Down
10 changes: 4 additions & 6 deletions docs/QG/QuickGuides.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
************************
Expand Down
Loading