@@ -49,17 +49,17 @@ statistics about instances' performance and activity quickly. These
4949are typically most useful for diagnosing issues and assessing normal
5050operation.
5151
52- :program:` mongotop`
53- ```````````````````
52+ `` mongotop` `
53+ ````````````
5454
5555:program:`mongotop` tracks and reports the current read and write
5656activity of a MongoDB instance. :program:`mongotop` provides
5757per-collection visibility into use. Use :program:`mongotop` to verify
5858that activity and use match expectations. See the :doc:`mongotop
5959manual </reference/mongotop>` for details.
6060
61- :program:` mongostat`
62- ````````````````````
61+ `` mongostat` `
62+ `````````````
6363
6464:program:`mongostat` captures and returns counters of database
6565operations. :program:`mongostat` reports operations on a per-type
@@ -85,15 +85,15 @@ locally running mongod instance: http://localhost:28017
8585Statistics
8686~~~~~~~~~~
8787
88- The :program:`mongo` shell provides a number of commands that return
88+ MongoDB provides a number of commands that return
8989statistics about the state of the MongoDB instance. These data may
9090provide finer granularity regarding the state of the MongoDB instance
9191than the tools above. Consider using their output in scripts and
9292programs to develop custom alerts, or modifying the behavior of your
9393application in response to the activity of your instance.
9494
95- serverStatus
96- ````````````
95+ `` serverStatus``
96+ ````````````````
9797
9898Access :doc:`serverStatus data </reference/server-status/>` by way of
9999the :dbcommand:`serverStatus` command. This :term:`document`
@@ -109,8 +109,8 @@ data provided by :dbcommand:`serverStatus`.
109109.. seealso:: :method:`db.stats()` and :doc:`serverStatus data
110110 </reference/server-status/>`.
111111
112- replSetGetStatus
113- ````````````````
112+ `` replSetGetStatus``
113+ ````````````````````
114114
115115View the :doc:`replSetGetStatus data </reference/replica-status>` with
116116the :dbcommand:`replSetGetStatus` command (:method:`rs.status()` from the
@@ -120,8 +120,8 @@ set. Use this data to ensure that replication is properly configured,
120120and to check the connections between the current host and the members
121121of the replica set.
122122
123- dbStats
124- ```````
123+ `` dbStats``
124+ ```````````
125125
126126The :doc:`dbStats data </reference/database-statistics>` is accessible
127127by way of the :dbcommand:`dbStats` command (:method:`db.stats()` from
@@ -133,8 +133,8 @@ of a specific database. This output also allows you to compare
133133utilization between databases and to determine average
134134:term:`document` size in a database.
135135
136- collStats
137- `````````
136+ `` collStats``
137+ `````````````
138138
139139The :doc:`collStats data </reference/collection-statistics>` is
140140accessible using the :dbcommand:`collStats` command (:method:`db.printCollectionStats()`
@@ -144,6 +144,19 @@ this includes a count of the objects in the collection, the size of
144144the collection, the amount of disk space used by the collection, and
145145information about the indexes.
146146
147+ Introspection Tools
148+ -------------------
149+
150+ In addition to status reporting, MongoDB provides a number of
151+ introspection tools that you can use to diagnose and analyze
152+ performance and operational conditions. Consider the following
153+ documentation:
154+
155+ - :dbcommand:`diagLogging`
156+ - :doc:`/tutorial/manage-the-database-profiler`
157+ - :doc:`/reference/database-profiler`
158+ - :doc:`/reference/current-op`
159+
147160Third Party Tools
148161~~~~~~~~~~~~~~~~~
149162
0 commit comments