[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   

Description

Compatibility 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 changes

Impact to Other Docs

MVP (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, DOCS-12069): Updating compatibility for 2.6 and 3.0 EOL
Branch: master
https://github.com/10gen/mms-docs/commit/d4b25af1d529489abcaf0bea49e40eb37adf11da

Comment by Anthony Sansone (Inactive) [ 22/Sep/18 ]

David,

Thank you for your questions. We will be making some changes based on them:

  1. Regarding the backing databases, that is covered currently on a separate page: Install the Ops Manager Application Database and Backup Database. We will update the compatibility matrix accordingly to clarify this concern.
  2. The table you point out on the Compatibility Matrix page will be updated to be in line with the Backing Database table. It provides more clarity.

To your questions specifically:

  1. Ops Manager 3.4.x can monitor any MongoDB database in the following versions:
    1. 2.4.3 to 2.4.14 (released 28 Apr 15, MongoDB 2.4.x was EOL as of 5 May 16)
    2. 2.6.0 to 2.6.12 (released 24 Mar 16, MongoDB 2.6.x was EOL as of 31 Oct 16)
    3. 3.0.0 to 3.0.15 (released 15 May 17, MongoDB 3.0.x was EOL as of 28 Feb 18)
    4. 3.2.0 to 3.2.21 (released 5 Sep 18)
    5. 3.4.0 to 3.4.17 (released 5 Sep 18)
  2. Ops Manager 3.4.x can use any MongoDB database in the following versions
    1. 3.0.8 to 3.0.15 (released 15 May 17, MongoDB 3.0.x was EOL as of 28 Feb 18)
    2. 3.2.0 to 3.2.21 (released 5 Sep 18)
    3. 3.4.0 to 3.4.17 (released 5 Sep 18)
  3. The latest MongoDB versions that Ops Manager 3.4.x can use include:
    1. Backing Databases
      1. 3.0.15 (released 15 May 17, MongoDB 3.0.x was EOL as of 28 Feb 18)
      2. 3.2.21 (released 5 Sep 18)
      3. 3.4.17 (released 5 Sep 18)
    2. Automate or Monitor
      1. 2.4.14 (released 28 Apr 15, MongoDB 2.4.x was EOL as of 5 May 16)
      2. 2.6.12 (released 24 Mar 16, MongoDB 2.6.x was EOL as of 31 Oct 16)
      3. 3.0.15 (released 15 May 17, MongoDB 3.0.x was EOL as of 28 Feb 18)
      4. 3.2.21 (released 5 Sep 18)
      5. 3.4.17 (released 5 Sep 18)

Again, thank you for your questions and we will update the documentation accordingly.

Anthony T. Sansone
Senior Technical Writer, Cloud and Enterprise Tools, MongoDB

Generated at Thu Feb 08 08:04:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.