Skip to content

Fix database profiler collection location #5438

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 11, 2021
Merged

Fix database profiler collection location #5438

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
4 changes: 2 additions & 2 deletions source/tutorial/manage-the-database-profiler.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,9 @@ The database profiler collects detailed information about
:ref:`database-commands` executed against a running :binary:`~bin.mongod`
instance. This includes CRUD operations as well as configuration and
administration commands.
The profiler writes all the data it collects to the
The profiler writes all the data it collects to a
:data:`system.profile <<database>.system.profile>` collection, a
:doc:`capped collection </core/capped-collections>` in the ``admin``
:doc:`capped collection </core/capped-collections>` in each profiled
database. See :doc:`/reference/database-profiler` for an overview of the
:data:`system.profile <<database>.system.profile>` documents created by
the profiler.
Expand Down