[DOCS-2498] Document the specific behaviour of each MMS Alert Created: 09/Jan/14 Updated: 16/Mar/15 Resolved: 13/Jun/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | v1.3.6 |
| Fix Version/s: | v1.3.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Days since reply: | 9 years, 24 weeks, 1 day ago | ||||||||||||||||||||
| Description |
|
We should have a section of the MMS documentation which details the specific behaviour of each alert and the criteria which trigger these alerts and how the configurables within each will be treated. This should be an easy to find section of the MMS doc's which we can give as a reference material for MMS alerts. |
| Comments |
| Comment by Githook User [ 02/Sep/14 ] | ||||||
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: | ||||||
| Comment by Githook User [ 02/Sep/14 ] | ||||||
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: | ||||||
| Comment by Githook User [ 02/Sep/14 ] | ||||||
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: | ||||||
| Comment by Githook User [ 02/Sep/14 ] | ||||||
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: | ||||||
| Comment by Githook User [ 16/Jun/14 ] | ||||||
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: | ||||||
| Comment by Githook User [ 16/Jun/14 ] | ||||||
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: | ||||||
| Comment by Githook User [ 16/Jun/14 ] | ||||||
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: | ||||||
| Comment by Githook User [ 16/Jun/14 ] | ||||||
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: | ||||||
| Comment by David Hows [ 28/Mar/14 ] | ||||||
|
Hey Guys, I invisioned this being something more along the lines of a table, which contains all of the artefacts specific to each alert. This way when end users wish to create alerts they can review the table and see all of the factors we use, then take these details into account for their own settings. We should also include all of the configurables that the end user can configure and explain them fully. Ideally we should also have one or two fully worked examples (for the whole page, not per alert) which show "how to think about this". Take the "Host Down" alert as an example.
| ||||||
| Comment by Githook User [ 28/Jan/14 ] | ||||||
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |