[DOCS-15853] [Atlas] Review documentation on Atlas profiler to clarify the node source of the profiling information Created: 27/Jan/23 Updated: 23/Mar/23 Resolved: 23/Mar/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Sheila Doyle | Assignee: | Corry Root |
| Resolution: | Done | Votes: | 0 |
| Labels: | cet-captain | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: | |
| Days since reply: | 45 weeks, 6 days ago |
| Story Points: | 2 |
| Description |
|
It seems that the atlas profiler when viewed at a cluster level takes its data from the primary log and the user needs to select each specific secondary node and view the profiler at a node level to see the long running queries on each secondary.
Requesting that this is clarified in the documentation,
I think the relevant page is here as this is linked when user selects the option to `view factors affecting (profiler) data
https://www.mongodb.com/docs/atlas/performance-advisor/#monitor-and-improve-slow-queries |
| Comments |
| Comment by Corry Root [ 23/Mar/23 ] |
|
sheila.doyle@mongodb.com, I added a note about the primary log and the Query Profiler. |
| Comment by Corry Root [ 23/Mar/23 ] |
|
sarah.simpers@mongodb.com, I added a note about the primary log and the Query Profiler. |