[DOCS-10122] Cloud Manager health score alert resolution URIs missing from the docs Created: 13/Apr/17  Updated: 03/May/17  Resolved: 28/Apr/17

Status: Closed
Project: Documentation
Component/s: Atlas, Cloud Manager
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Peter Gravelle Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 6 years, 41 weeks ago

 Description   

It seems that some Cloud Manager versions of Atlas alert resolution URLs don't exist. Specifically:

It seems that the Atlas versions do exist, though, i.e.:



 Comments   
Comment by Kay Kim (Inactive) [ 03/May/17 ]

Ah – thank you.

Comment by John Morales [ 03/May/17 ]

Hi kay@mongodb.com – so for the two Query Executor series I think the issue is they should just be "Query Executor: Scanned Objects is" and "Query Executor: Scanned is".

In short, Query Executor is the rates of scanned objects per second and scanned index keys per second, while Query Targeting are also scanned objects and scanned keys but scaled by the number of documents returned.

Comment by Michael Benoit [ 03/May/17 ]

kay.kim, missed your previous question until just now. Sorry about that!

john.morales would be the best person to answer that one.

Comment by Githook User [ 13/Apr/17 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-10122 query targeting alert resolution part 1
Branch: master
https://github.com/10gen/mms-docs/commit/981c3c15e143336c35d204759f7ecf482d6868cc

Comment by Kay Kim (Inactive) [ 13/Apr/17 ]

Thanks for the info. As such, for this ticket, I've just added the new page for query targeting alerts and am leaving the health-score page untouched.

Comment by Michael Benoit [ 13/Apr/17 ]

Keep in mind that the Health Score resolutions and the Alert Resolutions are two different things:

  • The Health Score email is a weekly email that includes about a dozen health checks that assess the health of your MongoDB deployment. For each check that does not pass (ie, "Replica set has less than three data bearing nodes"), we provide a link to the docs to help the user understand why this is important and how to fix it. Some of these checks may seem similar to the alert checks, but they're not the same.
  • The Alert Emails go out whenever an alert condition configured by the user is detected. These are configured by the user, and they target specific items in your deployment (ie, hosts, agents, backups, etc.). Some of these emails are quite detailed and include a description of the problem and a docs link to help the user fix it.

So no, I don't think these should be kept in sync since they're different concepts entirely.

Generated at Thu Feb 08 07:59:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.