[DOCS-15501] Setting a filter with db.setProfilingLevel(2) is not working Created: 25/Jul/22 Updated: 13/Nov/23 Resolved: 01/Aug/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0, 5.0.0, 6.0.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Peter Oh | Assignee: | Jason Price |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 27 weeks, 2 days ago |
| Epic Link: | DOCSP-11701 |
| Story Points: | 3 |
| Description |
|
Hello team, The below example is misleading, I have found out that this example is not working.
For example, the following db.setProfilingLevel() method sets for a mongod instance:
To me, the filter for Data Profiler works with db.setProfilingLevel( 1 ) only.
Which makes sense with the below description
https://www.mongodb.com/docs/manual/tutorial/manage-the-database-profiler/#database-profiler Can you please check this out and rectify the example? |
| Comments |
| Comment by Githook User [ 01/Aug/22 ] |
|
Author: {'name': 'jason-price-mongodb', 'email': '69260375+jason-price-mongodb@users.noreply.github.com', 'username': 'jason-price-mongodb'}Message:
Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com> Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com> |
| Comment by Githook User [ 01/Aug/22 ] |
|
Author: {'name': 'jason-price-mongodb', 'email': '69260375+jason-price-mongodb@users.noreply.github.com', 'username': 'jason-price-mongodb'}Message:
Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com> |