From 6fa8a3b261f88a76221058d8a8487a02cd8d8f5e Mon Sep 17 00:00:00 2001 From: Eric Milkie Date: Fri, 11 Jun 2021 14:11:56 -0400 Subject: [PATCH] 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. --- source/tutorial/manage-the-database-profiler.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/tutorial/manage-the-database-profiler.txt b/source/tutorial/manage-the-database-profiler.txt index 15ec80d4644..62b8bd39638 100644 --- a/source/tutorial/manage-the-database-profiler.txt +++ b/source/tutorial/manage-the-database-profiler.txt @@ -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 <.system.profile>` collection, a -:doc:`capped collection ` in the ``admin`` +:doc:`capped collection ` in each profiled database. See :doc:`/reference/database-profiler` for an overview of the :data:`system.profile <.system.profile>` documents created by the profiler.