[DOCS-2925] Clarify slowms setting with profile level 0 Created: 17/Mar/14 Updated: 27/Jul/16 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mark Helmstetter | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 8 years, 49 weeks, 5 days ago |
| Description |
|
Reading the docs page http://docs.mongodb.org/manual/tutorial/manage-the-database-profiler, it is not abundantly clear that a database with profiling level set to 0 will still log slow operations in the mongod log file. I think this needs to be clarified in several places on the page. The mongod options page does clearly state: "The database logs all slow queries to the log, even when the profiler is not turned on." We probably need something similar noted on the profiler page. |
| Comments |
| Comment by Mark Helmstetter [ 06/Mar/15 ] |
|
This page still has inaccurate and contradictory information. mongod always writes operations longer than the slowOpThresholdMs threshold to its log. But in several places we contract that. Perhaps the confusion is the distinction between the logging of slow queries to the mongod log and the profiler capturing slow queries – both of which have their slow threshold controlled by this single setting. Here are the places in the docs that are incorrect and/or confusing:
|
| Comment by Githook User [ 17/Mar/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 17/Mar/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |