Skip to content

Commit 377acb4

Browse files
milkieandf-mongodb
authored andcommitted
Fix database profiler collection location
I don't think we ever put everything in admin.system.profile, and the text already conflicts with itself later on when we do state that system.profile goes in every profiled database.
1 parent da35966 commit 377acb4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

source/tutorial/manage-the-database-profiler.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ The database profiler collects detailed information about
1616
:ref:`database-commands` executed against a running :binary:`~bin.mongod`
1717
instance. This includes CRUD operations as well as configuration and
1818
administration commands.
19-
The profiler writes all the data it collects to the
19+
The profiler writes all the data it collects to a
2020
:data:`system.profile <<database>.system.profile>` collection, a
21-
:doc:`capped collection </core/capped-collections>` in the ``admin``
21+
:doc:`capped collection </core/capped-collections>` in each profiled
2222
database. See :doc:`/reference/database-profiler` for an overview of the
2323
:data:`system.profile <<database>.system.profile>` documents created by
2424
the profiler.

0 commit comments

Comments
 (0)