@@ -1811,17 +1811,17 @@ Diagnostics
1811
1811
1812
1812
Replace ``<log>`` with one of the following values:
1813
1813
1814
- - ``global`` - to generate the most recent log events from the
1815
- database. This is equivalent to running the ``tail`` command on
1816
- the :program:`mongod` log in the system shell.
1814
+ - ``global`` - returns the combined output of all recent log
1815
+ entries.
1817
1816
1818
- - ``rs`` - if the :program:`mongod` is part of a :term:`replica set`,
1819
- :dbcommand:`getLog` will generate the most recent log events
1820
- that relate to replication processes .
1817
+ - ``rs`` - if the :program:`mongod` is part of a :term:`replica
1818
+ set`, :dbcommand:`getLog` will return recent notices related to
1819
+ replica set activity .
1821
1820
1822
- - ``startupWarnings`` - to generate logs that *may* contain
1821
+ - ``startupWarnings`` - will return logs that *may* contain
1823
1822
errors or warnings from MongoDB's log from when the current
1824
- process started.
1823
+ process started. If :program:`mongod` started without warnings,
1824
+ this filter may return an empty array.
1825
1825
1826
1826
You may also specify an asterisk (e.g. ``*``) as the ``<log>``
1827
1827
value to return a list of available log filters. The following
@@ -1834,8 +1834,8 @@ Diagnostics
1834
1834
{ "names" : [ "global", "rs", "startupWarnings" ], "ok" : 1 }
1835
1835
1836
1836
:dbcommand:`getLog` returns events from a RAM cache of the
1837
- :program:`mongod` events, and *does not* read log data from the log
1838
- file.
1837
+ :program:`mongod` events and *does not* read log data from the log
1838
+ : file.
1839
1839
1840
1840
.. dbcommand:: listDatabases
1841
1841
0 commit comments