[DOCS-438] Documentation should include suggested operational metrics to detect heavily loaded servers. Created: 23/Aug/12 Updated: 30/Oct/23 Resolved: 11/Oct/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | mongodb-2.2 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | William Zola | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 11 years, 18 weeks, 6 days ago | ||||
| Description |
|
MMS and other diagnostic tools (iostat, mongostat, mongotop) provide useful diagnostic information, but the documentation doesn't include any suggestions on what to monitor, what it means, or what levels of what key metrics indicate that there is a problem. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 11/Oct/12 ] |
|
Core issue addressed in existing documentation, feel free to reopen if there are specific issues with this documentation. |
| Comment by Sam Kleinman (Inactive) [ 02/Oct/12 ] |
|
http://docs.mongodb.org/manual/administration/monitoring/#diagnosing-performance-issues Are there specific improvements to this section that you'd make, I think this addresses the core concern. There's a lot of room for improvement, but I don't know if tickets like this are actionable. Cheers, |