Skip to content

DOCSP-17224 fix typos in log message docs #5491

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 30, 2021
Merged

DOCSP-17224 fix typos in log message docs #5491

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions source/reference/log-messages.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,7 +196,7 @@ specific instance of its subfield ``_id`` that triggered truncation
printed without data as ``{"_id":{}}``. The remainder of the ``request``
attribute is then omitted.

Log entires containing one or more truncated attributes include a
Log entries containing one or more truncated attributes include a
``truncated`` object which provides the following information for each
truncated attribute in the log entry:

Expand Down Expand Up @@ -240,7 +240,7 @@ Pretty Printing

.. include:: /includes/fact-use-jq-with-structured-logging.rst

You can use ``jq`` to pretty-print log entires as follows:
You can use ``jq`` to pretty-print log entries as follows:

- Pretty-print the entire log file:

Expand Down Expand Up @@ -683,7 +683,7 @@ the the amount of log messages MongoDB outputs. Verbosity levels can be
adjusted for all components together, or for specific
:ref:`named components <log-message-components>` individually.

Verbosity affects log entires in the :ref:`severity
Verbosity affects log entries in the :ref:`severity
<log-severity-levels>` categories **Informational** and **Debug** only.
Severity categories above these levels are always shown.

Expand Down Expand Up @@ -1017,7 +1017,7 @@ showing a client connection followed by a disconnection:
{"t":{"$date":"2020-06-01T13:06:59.027-0500"},"s":"I", "c":"NETWORK", "id":22943,"ctx":"listener","msg":"connection accepted from {session_remote} #{session_id} ({connectionCount}{word} now open)","attr":{"session_remote":"127.0.0.1:61298","session_id":164,"connectionCount":11,"word":" connections"}}
{"t":{"$date":"2020-06-01T13:07:03.490-0500"},"s":"I", "c":"NETWORK", "id":22944,"ctx":"conn157","msg":"end connection {remote} ({connectionCount}{word} now open)","attr":{"remote":"127.0.0.1:61298","connectionCount":10,"word":" connections"}}

The log IDs for these two entires are ``22943`` and ``22944``
The log IDs for these two entries are ``22943`` and ``22944``
respectively. You could then filter your log output to show only these
log IDs, effectively showing only client connection activity, using the
following ``jq`` syntax:
Expand All @@ -1035,7 +1035,7 @@ Filtering by Date Range
```````````````````````

Log output can be further refined by filtering on the timestamp field,
limiting log entires returned to a specific date range. For example,
limiting log entries returned to a specific date range. For example,
the following returns all log entries that occurred on April 15th, 2020:

.. code-block:: bash
Expand Down