[DOCS-10198] Add additional detail to explain alert "Backup job is too busy" Created: 02/May/17 Updated: 29/Oct/23 Resolved: 25/May/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | 3.4.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Annette Morrissey (Inactive) | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 33 weeks, 5 days ago |
| Epic Link: | C/OM Backup |
| Description |
|
A question was raised about what the alert "Backup job is too busy" actually means. A customer was unsure what threshold to set. Having a backup job that is too busy sounds like something they should know about, but they weren't sure what it means. I provided an answer based on consultation with A&I and https://jira.mongodb.org/browse/CLOUDP-7383. Can we incorporate some of the detail in CLOUDP-7383 into the docs: Thanks |
| Comments |
| Comment by Githook User [ 23/Jun/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: Added |
| Comment by Githook User [ 23/Jun/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: Added |
| Comment by Githook User [ 23/Jun/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: Added |
| Comment by Githook User [ 23/Jun/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: Added |