[DOCS-4216] Document that the "DELETE PROFILE DATA" button only clears the Web UI Cache Created: 21/Oct/14 Updated: 16/Mar/15 Resolved: 21/Nov/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.14 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | James O'Leary | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 12 weeks, 5 days ago |
| Description |
|
Add a note to the http://mms.mongodb.com/help-classic/tutorial/profile-database/ page to indicate that when the "DELETE PROFILING DATA" button is clicked, only the Web UI cache of the current profiling data is deleted. This data will be quickly populated with the same data if profiling is not disabled or the source profiling collection is dropped or cleared. |
| Comments |
| Comment by Githook User [ 21/Nov/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: |
| Comment by Bob Grabar [ 13/Nov/14 ] |
|
I've created this pull request: |