[DOCS-1403] Database profiler page incorrectly refers to "profiling level" as "log level" Created: 16/Apr/13 Updated: 30/Oct/23 Resolved: 16/Apr/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | J Rassi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 44 weeks, 1 day ago |
| Description |
|
The "Manage the database profiler" page uses the term "log level" when it's actually referring to "profiling level", which is misleading. The term "profiling level" should refer exclusively to the profiling subsystem, and the term "log level" should refer exclusively to the logging subsystem. |
| Comments |
| Comment by auto [ 16/Apr/13 ] |
|
Author: {u'date': u'2013-04-16T22:56:32Z', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: |