Skip to content

Commit 0dcc0b5

Browse files
author
Sam Kleinman
committed
DOCS-906
1 parent d60ef4c commit 0dcc0b5

File tree

1 file changed

+26
-13
lines changed

1 file changed

+26
-13
lines changed

source/administration/monitoring.txt

Lines changed: 26 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -49,17 +49,17 @@ statistics about instances' performance and activity quickly. These
4949
are typically most useful for diagnosing issues and assessing normal
5050
operation.
5151

52-
:program:`mongotop`
53-
```````````````````
52+
``mongotop``
53+
````````````
5454

5555
:program:`mongotop` tracks and reports the current read and write
5656
activity of a MongoDB instance. :program:`mongotop` provides
5757
per-collection visibility into use. Use :program:`mongotop` to verify
5858
that activity and use match expectations. See the :doc:`mongotop
5959
manual </reference/mongotop>` for details.
6060

61-
:program:`mongostat`
62-
````````````````````
61+
``mongostat``
62+
`````````````
6363

6464
:program:`mongostat` captures and returns counters of database
6565
operations. :program:`mongostat` reports operations on a per-type
@@ -85,15 +85,15 @@ locally running mongod instance: http://localhost:28017
8585
Statistics
8686
~~~~~~~~~~
8787

88-
The :program:`mongo` shell provides a number of commands that return
88+
MongoDB provides a number of commands that return
8989
statistics about the state of the MongoDB instance. These data may
9090
provide finer granularity regarding the state of the MongoDB instance
9191
than the tools above. Consider using their output in scripts and
9292
programs to develop custom alerts, or modifying the behavior of your
9393
application in response to the activity of your instance.
9494

95-
serverStatus
96-
````````````
95+
``serverStatus``
96+
````````````````
9797

9898
Access :doc:`serverStatus data </reference/server-status/>` by way of
9999
the :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

115115
View the :doc:`replSetGetStatus data </reference/replica-status>` with
116116
the :dbcommand:`replSetGetStatus` command (:method:`rs.status()` from the
@@ -120,8 +120,8 @@ set. Use this data to ensure that replication is properly configured,
120120
and to check the connections between the current host and the members
121121
of the replica set.
122122

123-
dbStats
124-
```````
123+
``dbStats``
124+
```````````
125125

126126
The :doc:`dbStats data </reference/database-statistics>` is accessible
127127
by 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
133133
utilization between databases and to determine average
134134
:term:`document` size in a database.
135135

136-
collStats
137-
`````````
136+
``collStats``
137+
`````````````
138138

139139
The :doc:`collStats data </reference/collection-statistics>` is
140140
accessible 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
144144
the collection, the amount of disk space used by the collection, and
145145
information 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+
147160
Third Party Tools
148161
~~~~~~~~~~~~~~~~~
149162

0 commit comments

Comments
 (0)