DOCSP-37078 SetAt for Diagnostics, Logging, and Health Parameters (#7… (#7781)

* DOCSP-37078 SetAt for Diagnostics, Logging, and Health Parameters (#7656)

* DOCSP-37078 SetAt for Diagnostic, Logging, and Health Parameters

* Adds setAt text

* Adds setAt text

* Adds setAt text

* Adds setAt text

* Adds setAt text

* Adds setAt text

* fixes build issue

* Fixes build issue

Author: kennethdyer

source/reference/parameters.txt

@@ -1674,6 +1674,8 @@ Logging Parameters
 
    The default :parameter:`logLevel` is ``0`` (Informational).
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
    The following example sets the :parameter:`logLevel` to ``2``:
 
    .. code-block:: javascript
@@ -1762,6 +1764,8 @@ Logging Parameters
      :setting:`storage.recovery
      <systemLog.component.storage.recovery.verbosity>`.
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
    For example, the following sets the :setting:`default verbosity
    level <systemLog.verbosity>` to ``1``, the :setting:`query
    <systemLog.component.query.verbosity>` to ``2``, the
@@ -1830,6 +1834,8 @@ Logging Parameters
       ``0``, may adversely affect system performance and negatively
       impact database operations.
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
    The following example sets the maximum log line size to ``20``
    kilobytes:
 
@@ -1853,6 +1859,8 @@ Logging Parameters
 
    - replication synchronization activities.
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
    Consider the following example which sets the
    ``quiet`` parameter to ``1``:
 
@@ -1924,6 +1932,8 @@ Logging Parameters
    for every database and socket C++ exception, for use with debugging.
    If ``true``, :binary:`~bin.mongod` will log full stack traces.
 
+   .. include:: /includes/fact-runtime-parameter
+
    Consider the following example which sets the
    ``traceExceptions`` to ``true``:
 
@@ -1951,14 +1961,15 @@ Logging Parameters
    ``suppressNoTLSPeerCertificateWarning`` to ``1`` or ``true`` to
    suppress those warnings.
 
+   .. include:: /includes/fact-startup-parameter
+
    The following operation sets ``suppressNoTLSPeerCertificateWarning``
    to ``true``:
 
    .. code-block:: bash
 
       db.adminCommand( { setParameter: 1, suppressNoTLSPeerCertificateWarning: true} )
 
-
 .. _param-ftdc:
 
 Diagnostic Parameters
@@ -2006,6 +2017,8 @@ The following parameters support diagnostic data capture (FTDC):
    Determines whether to enable the collecting and logging of data for
    diagnostic purposes. Diagnostic logging is enabled by default.
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
    For example, the following disables the diagnostic collection:
 
    .. code-block:: bash
@@ -2045,6 +2058,8 @@ The following parameters support diagnostic data capture (FTDC):
    name already exists in the path or if the process does not have permissions 
    to create the directory.
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
 .. parameter:: diagnosticDataCollectionDirectorySizeMB
 
    |both|
@@ -2058,6 +2073,8 @@ The following parameters support diagnostic data capture (FTDC):
    diagnostic files in the directory are automatically deleted based on
    the timestamp in the file name.
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
    For example, the following sets the maximum size of the directory to
    ``250`` megabytes:
 
@@ -2079,10 +2096,11 @@ The following parameters support diagnostic data capture (FTDC):
 
    *Default*: 10
 
-
    Specifies the maximum size, in megabytes, of each diagnostic
    file. If the file exceeds the maximum file size, MongoDB creates a new file.
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
    For example, the following sets the maximum size of each diagnostic
    file to ``20`` megabytes:
 
@@ -2104,6 +2122,8 @@ The following parameters support diagnostic data capture (FTDC):
    Specifies the interval, in milliseconds, at which to collect
    diagnostic data.
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
    For example, the following sets the interval to
    ``5000`` milliseconds or 5 seconds:
 
@@ -4266,6 +4286,8 @@ Health Manager Parameters
    ``critical``, the server waits for the specified interval 
    before removing the ``mongos`` from the cluster. 
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
    .. include:: /includes/example-activeFaultDurationSecs.rst
 
 .. parameter:: healthMonitoringIntensities
@@ -4276,6 +4298,8 @@ Health Manager Parameters
 
    Use this parameter to set intensity levels for |HMS|.
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
    .. include:: /includes/fact-healthMonitoringIntensities-values-array.rst
 
    Health Managers 
@@ -4297,6 +4321,8 @@ Health Manager Parameters
    |mongos-only|
 
    How often this |HM| will run, in milliseconds.
+
+   .. include:: /includes/fact-runtime-startup-parameter
 
    .. include:: /includes/fact-healthMonitoringIntervals-values-array.rst
 
@@ -4314,6 +4340,8 @@ Health Manager Parameters
 
    .. include:: /includes/fact-progressMonitor.rst
 
+   .. include:: /includes/fact-runtime-startup-parameter
+
    ``progressMonitor`` Fields
    ``````````````````````````
 

source/release-notes/4.4.txt

@@ -1559,7 +1559,7 @@ inside a transaction:
 For more details, see :ref:`transactions-create-collections-indexes`.
 
 MongoDB 4.4 adds a new parameter
-:parameter:`shouldMultiDocTxnCreateCollectionAndIndexes` which can
+``shouldMultiDocTxnCreateCollectionAndIndexes`` which can
 enable (default) or disable collection and index creation inside a
 transaction. When setting the parameter for a sharded cluster, set
 the parameter on all shards.