[DOCS-12069] Update Compatibility Charts for Ops Manager Created: 21/Sep/18 Updated: 29/Oct/23 Resolved: 25/Sep/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | David Mumladze | Assignee: | Jeffrey Allen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 5 years, 20 weeks, 1 day ago |
| Epic Link: | DOCSP-1743 |
| Story Points: | 1 |
| Description |
DescriptionCompatibility matrix shows that Ops Manager v3.4 can support min version of MongoDB v3.4, but does this mean it can monitor v3.4 MongoDB, or does this mean it can have v3.4 as a backing storage? In other words: a) Can I use Ops Manager v3.4.3.402 to monitor MongoDB 3.6.6. database b) Can Ops Manager vv3.4.3.402 have MongoDB 3.6.6 as a backing storage? c) What is the max version of MongoDB that Ops Manager vv3.4.3.402 can work with as monitor or as a backing storage?
Thank you. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by David Mumladze [ 25/Sep/18 ] |
|
Hi Tony, Thanks for clarifying. Ops Manager v.3.4 with backing storage v3.4 seems to be able to monitor MongoDB deployment v3.6 without issues. |
| Comment by Githook User [ 25/Sep/18 ] |
|
Author: {'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}Message: (DOCSP-3352, |
| Comment by Anthony Sansone (Inactive) [ 22/Sep/18 ] |
|
David, Thank you for your questions. We will be making some changes based on them:
To your questions specifically:
Again, thank you for your questions and we will update the documentation accordingly. Anthony T. Sansone |