[DOCS-194] better explanation of what slowms is used for Created: 27/Apr/12 Updated: 30/Oct/23 Due: 04/May/12 Resolved: 30/Apr/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kevin Matulef | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 11 years, 42 weeks, 2 days ago |
| Description |
|
In the documentation it's not super clear that even if the profiler is off, queries which take longer than the "slowms" value will get written to the log. The db.setProfilingLevel command only affects what gets written to the system.profile collection (although the slowms value affects what gets written to the logs too). I just updated the old documentation in two places to reflect this. The new docs are clear in one place, but not where the "--slowms" command line option is mentioned. |
| Comments |
| Comment by Kevin Matulef [ 30/Apr/12 ] |
|
LGTM. Thanks. |
| Comment by Sam Kleinman (Inactive) [ 30/Apr/12 ] |
|
I'm going to publish this change and resolve this ticket, but if you think that I've missed something, I'm more than willing to expand further. |
| Comment by auto [ 30/Apr/12 ] |
|
Author: {u'login': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |