DOCSP-42223-updates-performance-page-v6.0-backport (9379) (#9470)

* DOCSP-42223-updates-performance-page (#9379)

* Moves FTDC into its own page

* Revises performance page to include Atlas

* Updates table of contents to include FTDC page

* Removes FTDC link from general perf page

* Reformats page to closer match concept template

(cherry picked from commit ded49f9)

# Conflicts:
#	source/administration/analyzing-mongodb-performance.txt

* Adds permissions include

* Remove database profiler section

Author: jwilson-mdb

source/administration/analyzing-mongodb-performance.txt

@@ -49,6 +49,12 @@ affecting your performance, refer to the :ref:`server-status-locks`
 section and the :ref:`globalLock` section of the
 :dbcommand:`serverStatus` output.
 
+.. note::
+   Some ``serverStatus`` response fields are not returned on 
+   {+atlas+} M0/M2/M5 clusters. For more information, see 
+   :ref:`free-shard-commands-with-limits` in the {+atlas+} 
+   documentation.
+
 Dividing :serverstatus:`locks.<type>.timeAcquiringMicros` by
 :serverstatus:`locks.<type>.acquireWaitCount`
 can give an approximate average wait time for a particular lock mode.
@@ -102,158 +108,27 @@ reuse connections more efficiently. An extremely high number of
 connections, particularly without corresponding workload, is often
 indicative of a driver or other configuration error.
 
+Self-Managed Connection Limits
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
 Unless constrained by system-wide limits, the maximum number of
 incoming connections supported by MongoDB is configured with the
 :setting:`~net.maxIncomingConnections` setting. On Unix-based systems,
 system-wide limits can be modified using the ``ulimit`` command, or by
 editing your system's ``/etc/sysctl`` file. See :doc:`/reference/ulimit`
 for more information.
 
-.. _database-profiling:
-
-Database Profiling
-------------------
-
-The :doc:`/tutorial/manage-the-database-profiler` collects detailed
-information about operations run against a mongod instance. The
-profiler's output can help to identify inefficient queries and
-operations.
-
-You can enable and configure profiling for individual databases or for
-all databases on a :binary:`~bin.mongod` instance.
-Profiler settings affect only a single :binary:`~bin.mongod` instance and
-will not propagate across a :term:`replica set` or :term:`sharded
-cluster`.
-
-See :doc:`/tutorial/manage-the-database-profiler` for information on
-enabling and configuring the profiler.
-
-The following profiling levels are available:
-
-.. include:: /includes/database-profiler-levels.rst
-
-.. include:: /includes/warning-profiler-performance.rst
-
-.. note::
-
-   .. include:: /includes/fact-log-slow-queries.rst
-   
-.. include:: /includes/extracts/4.2-changes-log-query-shapes-plan-cache-key.rst
-
-.. _ftdc-stub:
-
-Full Time Diagnostic Data Capture
----------------------------------
-
-To help MongoDB engineers analyze server behavior, :binary:`~bin.mongod` and
-:binary:`~bin.mongos` processes include a Full Time Diagnostic Data
-Capture (FTDC) mechanism. FTDC is enabled by default. Due to its
-importance in debugging deployments, FTDC thread failures are fatal and
-stop the parent ``mongod`` or ``mongos`` process.
-
-.. important:: FTDC Privacy
-
-   FTDC data files are compressed and not human-readable. MongoDB Inc.
-   engineers cannot access FTDC data without explicit permission
-   and assistance from system owners or operators.
-
-   FTDC data **never** contains any of the following information:
-
-   - Samples of queries, query predicates, or query results
-   - Data sampled from any end-user collection or index
-   - System or MongoDB user credentials or security certificates
-
-   FTDC data contains certain host machine information such as
-   hostnames, operating system information, and the options or settings
-   used to start the :binary:`mongod <bin.mongod>` or 
-   :binary:`mongos <bin.mongos>`. This information may be
-   considered protected or confidential by some organizations or
-   regulatory bodies, but is not typically considered to be Personally
-   Identifiable Information (PII). For clusters where these fields were
-   configured with protected, confidential, or PII data, please notify
-   MongoDB Inc. engineers before sending the FTDC data so appropriate
-   measures can be taken.
-
-FTDC periodically collects statistics produced by the following 
-commands:
-
-- :dbcommand:`serverStatus`
-- :dbcommand:`replSetGetStatus` (:binary:`mongod <bin.mongod>` only)
-- :dbcommand:`collStats` for the :data:`local.oplog.rs` collection (:binary:`mongod <bin.mongod>` only)
-- :dbcommand:`connPoolStats` (:binary:`mongos <bin.mongos>` only)
-
-Depending on the host operating system, the diagnostic data may include
-one or more of the following utilization statistics:
-
-- CPU utilization
-- Memory utilization
-- Disk utilization related to performance. FTDC does not include
-  data related to storage capacity.
-- Network performance statistics. FTDC only captures metadata and
-  does not capture or inspect any network packets.
-
-.. note::
-
-   If the :binary:`~bin.mongod` process runs in a :term:`container`, FTDC 
-   reports utilization statistics from the perspective of the container 
-   instead of the host operating system. For example, if a the 
-   :binary:`~bin.mongod` runs in a container that is configured with RAM 
-   restrictions, FTDC calculates memory utilization against the container's 
-   RAM limit, as opposed to the host operating system's RAM limit.
-
-FTDC collects statistics produced by the following commands on
-file rotation or startup:
-
-- :dbcommand:`getCmdLineOpts`
-- :dbcommand:`buildInfo`
-- :dbcommand:`hostInfo`
-
-:binary:`mongod <bin.mongod>` processes store FTDC data files in a 
-``diagnostic.data`` directory under the instances 
-:setting:`storage.dbPath`. All diagnostic data files are stored
-under this directory. For example, given a :setting:`~storage.dbPath`
-of ``/data/db``, the diagnostic data directory would be
-``/data/db/diagnostic.data``. 
-
-:binary:`mongos <bin.mongos>` processes store FTDC data files in a 
-diagnostic directory relative to the :setting:`systemLog.path` log 
-path setting. MongoDB truncates the logpath's file extension and 
-concatenates ``diagnostic.data`` to the remaining name. For example, 
-given a :setting:`~systemLog.path` setting of
-``/var/log/mongodb/mongos.log``, the diagnostic data directory would be 
-``/var/log/mongodb/mongos.diagnostic.data``.
-
-FTDC runs with the following defaults:
-
-- Data capture every 1 second
-- 200MB maximum ``diagnostic.data`` folder size. 
-
-These defaults are designed to provide useful data to MongoDB Inc. 
-engineers with minimal impact on performance or storage size. These 
-values only require modifications if requested by MongoDB Inc. engineers 
-for specific diagnostic purposes.
-
-You can view the FTDC source code on the
-`MongoDB Github Repository <https://github.com/mongodb/mongo/tree/master/src/mongo/db/ftdc>`_.
-The ``ftdc_system_stats_*.ccp`` files specifically define any
-system-specific diagnostic data captured.
-
-To disable FTDC, start up the :binary:`mongod <bin.mongod>` or 
-:binary:`mongos <bin.mongos>` with the 
-``diagnosticDataCollectionEnabled: false`` option specified to the 
-:setting:`setParameter` setting in your configuration file:
 
-.. code-block:: yaml
+{+atlas+} Connection Limits
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-   setParameter:
-     diagnosticDataCollectionEnabled: false
+{+atlas+} sets the limit for concurrent incoming connections based on 
+the cluster tier and class. To learn more, see :ref:`<connection-limits>` 
+in the Atlas documentation.
 
-Disabling FTDC may increase the time or resources required when 
-analyzing or debugging issues with support from MongoDB Inc. engineers. 
 
 .. toctree::
    :titlesonly:
    :hidden:
 
    Connection Pool </administration/connection-pool-overview>
-    

source/administration/full-time-diagnostic-data-capture.txt

@@ -0,0 +1,149 @@
+.. _self-managed-ftdc:
+.. _ftdc-stub:
+
+=================================
+Full Time Diagnostic Data Capture
+=================================
+
+.. facet::
+   :name: genre
+   :values: reference
+
+.. default-domain:: mongodb
+
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 1
+   :class: singlecol
+
+To help MongoDB engineers analyze server behavior, :binary:`~bin.mongod` and
+:binary:`~bin.mongos` processes include a Full Time Diagnostic Data
+Capture (FTDC) mechanism. FTDC is enabled by default. Due to its
+importance in debugging deployments, FTDC thread failures are fatal and
+stop the parent ``mongod`` or ``mongos`` process.
+
+Behavior
+--------
+
+.. note:: FTDC User Permissions on Windows
+   
+   .. include:: /includes/fact-ftdc-windows-user-permissions.rst
+
+FTDC periodically collects statistics produced by the following 
+commands:
+
+- :dbcommand:`serverStatus`
+- :dbcommand:`replSetGetStatus` (:binary:`mongod <bin.mongod>` only)
+- :dbcommand:`collStats` for the :data:`local.oplog.rs` collection (:binary:`mongod <bin.mongod>` only)
+- :dbcommand:`connPoolStats` (:binary:`mongos <bin.mongos>` only)
+
+Depending on the host operating system, the diagnostic data may include
+one or more of the following utilization statistics:
+
+- CPU utilization
+- Memory utilization
+- Disk utilization related to performance. FTDC does not include
+  data related to storage capacity.
+- Network performance statistics. FTDC only captures metadata and
+  does not capture or inspect any network packets.
+
+.. note::
+
+   If the :binary:`~bin.mongod` process runs in a :term:`container`, FTDC 
+   reports utilization statistics from the perspective of the container 
+   instead of the host operating system. For example, if a the 
+   :binary:`~bin.mongod` runs in a container that is configured with RAM 
+   restrictions, FTDC calculates memory utilization against the container's 
+   RAM limit, as opposed to the host operating system's RAM limit.
+
+FTDC collects statistics produced by the following commands on
+file rotation or startup:
+
+- :dbcommand:`getCmdLineOpts`
+- :dbcommand:`buildInfo`
+- :dbcommand:`hostInfo`
+
+FTDC Data Files
+~~~~~~~~~~~~~~~
+
+:binary:`mongod <bin.mongod>` processes store FTDC data files in a 
+``diagnostic.data`` directory under the instances 
+:setting:`storage.dbPath`. All diagnostic data files are stored
+under this directory. For example, given a :setting:`~storage.dbPath`
+of ``/data/db``, the diagnostic data directory would be
+``/data/db/diagnostic.data``. 
+
+:binary:`mongos <bin.mongos>` processes store FTDC data files in a 
+diagnostic directory relative to the :setting:`systemLog.path` log 
+path setting. MongoDB truncates the logpath's file extension and 
+concatenates ``diagnostic.data`` to the remaining name. For example, 
+given a :setting:`~systemLog.path` setting of
+``/var/log/mongodb/mongos.log``, the diagnostic data directory would be 
+``/var/log/mongodb/mongos.diagnostic.data``.
+
+FTDC Privacy
+~~~~~~~~~~~~
+
+FTDC data files are compressed and not human-readable. They inherit
+the same file access permissions as the MongoDB data files. Only
+users with access to FTDC data files can transmit the FTDC data.
+
+MongoDB engineers cannot access FTDC data without explicit
+permission and assistance from system owners or operators.
+
+FTDC data **never** contains any of the following information:
+
+- Samples of queries, query predicates, or query results
+- Data sampled from any end-user collection or index
+- System or MongoDB user credentials or security certificates
+
+FTDC data contains certain host machine information such as
+hostnames, operating system information, and the options or settings
+used to start the :binary:`mongod <bin.mongod>` or 
+:binary:`mongos <bin.mongos>`. This information may be
+considered protected or confidential by some organizations or
+regulatory bodies, but is not typically considered to be Personally
+Identifiable Information (PII). For clusters where these fields are
+configured with protected, confidential, or PII data, please notify
+MongoDB engineers before sending FTDC data to coordinate
+appropriate security measures.
+
+Details
+-------
+
+You can view the FTDC source code on the
+`MongoDB Github Repository <https://github.com/mongodb/mongo/tree/master/src/mongo/db/ftdc>`_.
+The ``ftdc_system_stats_*.ccp`` files specifically define any
+system-specific diagnostic data captured.
+
+FTDC Defaults
+~~~~~~~~~~~~~
+
+FTDC runs with the following defaults:
+
+- Data capture every 1 second
+- 200MB maximum ``diagnostic.data`` folder size. 
+
+These defaults are designed to provide useful data to MongoDB 
+engineers with minimal impact on performance or storage size. These 
+values only require modifications if requested by MongoDB engineers 
+for specific diagnostic purposes.
+
+Disable FTDC
+~~~~~~~~~~~~
+
+To disable FTDC, start up the :binary:`mongod <bin.mongod>` or 
+:binary:`mongos <bin.mongos>` with the 
+``diagnosticDataCollectionEnabled: false`` option in the 
+:setting:`setParameter` settings of your configuration file:
+
+.. code-block:: yaml
+
+   setParameter:
+     diagnosticDataCollectionEnabled: false
+
+Disabling FTDC may increase the time or resources required when 
+analyzing or debugging issues with support from MongoDB engineers. 
+For information on MongoDB Support, visit `Get Started With MongoDB Support <https://www.mongodb.com/support/get-started?tck=docs_server>`_.
+ 

source/administration/self-managed-performance.txt

@@ -13,3 +13,4 @@ Self-Managed Performance
    Disable Transparent Hugepages </tutorial/transparent-huge-pages>
    Health Managers </administration/health-managers>
    UNIX ulimit </reference/ulimit>
+   Full Time Diagnostic Data Capture </administration/full-time-diagnostic-data-capture>

source/includes/fact-ftdc-windows-user-permissions.rst

@@ -0,0 +1,9 @@
+On Windows, to collect system data such as disk, cpu, and memory, FTDC requires Microsoft access permissions from the following groups:
+
+- Performance Monitor Users
+
+- Performance Log Users 
+
+If the user running :binary:`mongod <bin.mongod>` and :binary:`mongos
+<bin.mongos>` is not an administrator, add them to these groups to log
+FTDC data. For more information, see `the Microsoft documentation here <https://learn.microsoft.com/en-us/windows/win32/perfctrs/restricting-access-to-performance-extension--dlls>`_.

source/tutorial/manage-the-database-profiler.txt

@@ -1,4 +1,5 @@
 .. _database-profiler:
+.. _database-profiling:
 
 =================
 Database Profiler