@@ -2751,19 +2751,28 @@ shardingStatistics
2751
2751
2752
2752
.. include:: /includes/fact-server-status-num-hosts-targeted.rst
2753
2753
2754
- .. note:: Running the :dbcommand:`serverStatus` on :binary:`mongos`
2755
- will provide insight into the aggregation operations find,
2756
- insert, update, delete and aggregate that run on a sharded
2757
- cluster.
2758
-
2759
- Multi-shard operations can either be
2760
- :ref:`scatter-gather<sharding-query-patterns>`
2761
- or shard specific. Multi-shard scatter-gather operations can
2762
- :ref:`consume more resources<sharding-troubleshooting-scatter-gather>`,
2763
- by using the
2764
- :serverstatus:`shardingStatistics.numHostsTargeted`
2765
- metrics you can tune the aggregation queries that run on a
2766
- sharded cluster.
2754
+ .. serverstatus:: shardingStatistics.numHostsTargeted
2755
+
2756
+ Indicates the number of shards targeted for ``CRUD`` operations and
2757
+ aggregation commands. When a ``CRUD`` operation or aggregation
2758
+ command is run, the following metrics will be incremented.
2759
+
2760
+ .. include:: /includes/fact-server-status-num-hosts-targeted.rst
2761
+
2762
+ .. note::
2763
+
2764
+ Running the :dbcommand:`serverStatus` command on :binary:`mongos`
2765
+ will provide insight into the CRUD and aggregation operations that
2766
+ run on a sharded cluster.
2767
+
2768
+ Multi-shard operations can either be
2769
+ :ref:`scatter-gather<sharding-query-patterns>`
2770
+ or shard specific. Multi-shard scatter-gather operations can
2771
+ :ref:`consume more resources<sharding-troubleshooting-scatter-gather>`.
2772
+ By using the
2773
+ :serverstatus:`shardingStatistics.numHostsTargeted`
2774
+ metrics you can tune the aggregation queries that run on a
2775
+ sharded cluster.
2767
2776
2768
2777
shardedIndexConsistency
2769
2778
~~~~~~~~~~~~~~~~~~~~~~~
0 commit comments