441 results found

1. Include CPU usage in Sharded Cluster Monitoring Overview

   In the sharded cluster monitoring overview it would be useful to also have the option to display the Process CPU usage to quickly identify shards which have a higher CPU load. Other hardware metrics might be useful as well.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Allow multiple authentication sources simultaneously

   Currently Ops Manager authentication supports either the Application Database, LDAP, or SAML, but these methods cannot be combined. Ideally we would like to move to LDAP, but we are stuck with the local authentication method as we depend on a local admin user which is used when first deploying and configuring the Ops Manager ecosystem. We also do not want to depend solely on the availability of the LDAP servers regarding an admin user. The MongoDB cluster deployments do support multiple authentication methods at the same time (we have local admin and monitoring accounts while users are authenticating via LDAP), it would be great if you could allow the same setup for Ops Manager.

   Currently Ops Manager authentication supports either the Application Database, LDAP, or SAML, but these methods cannot be combined. Ideally we would like to move to LDAP, but we are stuck with the local authentication method as we depend on a local admin user which is used when first deploying and configuring the Ops Manager ecosystem. We also do not want to depend solely on the availability of the LDAP servers regarding an admin user. The MongoDB cluster deployments do support multiple authentication methods at the same time (we have local admin and monitoring accounts while users are authenticating via LDAP),… more

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Sharding

   When we create a new collection with a shard key using mongosh the same is not reflected in cloud manager. In cloud manager / ops manager the shard key for the new collection is not seen in the shard tab.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cloud Manager  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Loadbalance functionality for Ops Manager

   When Ops Manager is under heavy load from many active database services, f.e. to handle backup snapshots, the recommendation from the case support portal is to use a loadbalancer in front of Ops Manager.
   It would be great, if Ops Manager could have this as an integrated functionality to forward connections from agents to additional Ops Manager instances.
   Background: Our nTSE did confirm, that we could set a different Ops Manager URL in the agent config, but the transferred data from this agent is still sent to the initially configured Ops Manager instance.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Include "Fetch Time" in Profiler timings

   When we run the Profiler, the runtime of "select" type queries are dramatically understated. This is because the Profiler only counts the time of the "query", and doesn't include how long it took to "fetch" the result set.

   In one of our test cases, we "tuned" the query so it only shows as running 82 ms in the Profiler. However, when we actually run this same query in JavaScript, the runtime is 10 seconds. This is a very slow query which our end users experience many times a day.

   Is there a way to configure Profiler to be more realistic, and include the "fetch time" as well as the "query" time?

   Currently, the Profiler seems to be of little us in finding slow queries. We have to find them using other means.

   Thank you.

   When we run the Profiler, the runtime of "select" type queries are dramatically understated. This is because the Profiler only counts the time of the "query", and doesn't include how long it took to "fetch" the result set.

   In one of our test cases, we "tuned" the query so it only shows as running 82 ms in the Profiler. However, when we actually run this same query in JavaScript, the runtime is 10 seconds. This is a very slow query which our end users experience many times a day.

   Is there a way to configure Profiler to be more realistic,… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Monitoring / Alerts  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Profiler and Performance Advisor without Automation

   Currently it is required to enable automation on a cluster in order use the Profiler/Performance Advisor.

   https://docs.opsmanager.mongodb.com/current/tutorial/profile-database/

   https://docs.opsmanager.mongodb.com/current/tutorial/performance-advisor/

   As automation is sometimes not desired for a cluster, please add the ability to Profile Databases and use Performance Advisor when a cluster is monitored only.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Add command for suspending automation

   Add command for suspending automation (similar to what we have for unmanage)

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  MongoDB CLI for Cloud Manager and Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Do not start backups for Sharded clusters unless all requirements are met

   With FCV > 4.2, Backups requires the backup module to be activated on at least one member per shard for sharded clusters but it also doesn't stop one from starting backups if the backup module is activated only on one member of the entire sharded cluster, for example, activating the backup module on a single member of the config server replica set and not on any member of the shards allow for one to start backups.

   Currently, if backups are enabled and at least one of the Replica sets in the Cluster has a backup module, backups will start for the cluster.
   The backups in the "missing" backup agent function scenario would not be consistent.

   With FCV > 4.2, Backups requires the backup module to be activated on at least one member per shard for sharded clusters but it also doesn't stop one from starting backups if the backup module is activated only on one member of the entire sharded cluster, for example, activating the backup module on a single member of the config server replica set and not on any member of the shards allow for one to start backups.

   Currently, if backups are enabled and at least one of the Replica sets in the Cluster has a backup module, backups will start for… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Improvement of Restore Process in Ops Manager

   Presently Ops manager restore process removes all the data from the target MongoDb deployment and then restores from the user selected Snapshot and subsequently applies the PIT restore.
   
   It is noted that time taken by the restore operations increases as and when the DB size increases. The restore operation would also require the Applications to be shutdown and this would lead to increase in Application downtime during the restore process.

   In order to minimize the downtime we need to reduce the restore time.

   One suggestion to reduce the restore time is to perform automated restore from the latest available snapshots to the standby replica set(Managed by Ops Manager) on regular basis and then perform only the Point In Time Recovery which would only apply the Oplog changes from the latest restored snapshot to the standby replica set and do not delete the data before performing the restore from the target replica set. This would help pointing the applications immediately to the standby replica set after the PIT is completed and minimize the downtime.

   For this the restore operation should have a feature for user to select if the data in the target replica set should be removed or not before performing the PIT restore.

   Scheduling the restore operations from the latest available snapshots on the standby replica set and then performing only the PIT restore from the last available snapshot whenever required without deleting the data from the standby replica set would help restoring the Application data faster.

   Presently Ops manager restore process removes all the data from the target MongoDb deployment and then restores from the user selected Snapshot and subsequently applies the PIT restore.
   
   It is noted that time taken by the restore operations increases as and when the DB size increases. The restore operation would also require the Applications to be shutdown and this would lead to increase in Application downtime during the restore process.

   In order to minimize the downtime we need to reduce the restore time.

   One suggestion to reduce the restore time is to perform automated restore from the latest available snapshots… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Ops Manager global actions (mongocli ops-manager admin)

    Add cli commands in global scope of Ops Manager to allow for scripting actions on all projects (e.g. update all agents after an upgrade of Ops Manager):
    - CRUD projects (prio on get projects to allow for looping over them)
    - CRUD orgs
    - CRUD users
    - global config managemant
    - global alert management

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  MongoDB CLI for Cloud Manager and Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Present MongoDB clients metadata on Ops Manager UI

    Before MongoDB version upgrades we should verify all drivers compatibility for the new version.

    It is sometimes difficult to track all of the drivers used connecting to the deployments. Currently it requires parsing of multiple mongos/mongod logs for client connections or internal code investigations.

    Suggestion

    It may be beneficial to collect and present clients statistics (version, type, IP) data on Ops Manager.

    Maybe this could be a feature that can be toggled on demand.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Combine Support Portal Mailing Lists when opening cases

    Combine different Mailing Lists in the Support Portal, when opening a case. Right now you can use only one Mailing List per case. When opening cases it would be good to choose to send updates to 2 or more mailing lists depending on the audience required. So rather than creating a new mailing list for every possible combination of recipients, choosing more than one mailing list per case, would enable the right people to get updates and reduce the noise for others. E.g. Operations + Project A Mailing list if it only concerns that one project, and Operations + Project A + Project B if it concerns all projects.

    Combine different Mailing Lists in the Support Portal, when opening a case. Right now you can use only one Mailing List per case. When opening cases it would be good to choose to send updates to 2 or more mailing lists depending on the audience required. So rather than creating a new mailing list for every possible combination of recipients, choosing more than one mailing list per case, would enable the right people to get updates and reduce the noise for others. E.g. Operations + Project A Mailing list if it only concerns that one project, and Operations + Project… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. System Statistics without Automation

    Currently it is required to enable automation on a cluster in order to monitor system level statistics such as CPU.

    As automation is sometimes not desired for a cluster, please add the ability to gather system level metrics when a cluster is monitored only.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. OpsManager Application DataBase Backup and Restore

    Ops Manager Application needs a way to backup and restore AppDB without Ops Manager Downtime to recover from infrastructure failures or fatal errors.

    31 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. connection

    Ops Manager only shows number of connection. Most DB monitoring tool shows where the connection is coming from and whats being run from the session. This needs to be a part of Ops Manager

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Monitoring / Alerts  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. modify mongoDB DB user in ATLAS, OPS Manager , or Cloud Manager

    It would be really nice if mongocli could be used to modify user accounts. Add new roles, or change the password. Currently mongocli can add, list , delete project DB user accounts. It would be nice for modify, since there is a need for password rotation, and mongocli see so fit that bill quite nicely.

    This is for OPS Manager, but could be for OPS , Cloud or Atlas..

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  MongoDB CLI for Cloud Manager and Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Increase maximum retention periof of backups

    Currently OpsManager's maximum retention period for backups is 84 months (7 years). We have the requirement to keep 10 years of backups, hence adding some values (96, 108, 120, 132, 144) in the "Store monthly snapshots for... months" in the backup schedule would be helpful. Another option might be to allow custom values (I guess this is the purpose of https://feedback.mongodb.com/forums/924355-ops-tools/suggestions/39441955-make-snapshot-retention-policy-more-customisable)

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Ops Manager to support Credentials Cache to connect to APP DB

    Ops Manager to support Credentials Cache to connect to APP DB
    Its related to case opened : Case: 00881812

    Also change alerting ( Email Subject )

    Currently we get alert with email subject as below even if issue is resolved
    System Alert - Backing Database Connection is Unhealthy

    We Should change alert email subject to Say "Healthy " instead of "Unhealthy " when issue is resolved.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. export & import alerts settings from one project to another project

    export & import alerts settings from one project to another project

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Monitoring / Alerts  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. MongoDB Agent (Automation Module): don't attempt to auth with `net.tls.clusterFile` / `net.tls.certificateKeyFile` and use Agent X.509 cert

    Problem Statement,
    What is the problem? MongoDB Agent (Automation Module) attempts to auth with net.tls.clusterFile / net.tls.certificateKeyFile X.509 certificate first, pretending it is a Replica Set member.

    Why is this a problem? MongoDB Server process logs are flooded by unnecessary noise from such MongoDB Agent (Automation Module) auth attempts pretending it is Replica Set member. MongoDB Server will always log Replica Set member auth certificate usage outside of internal MongoDB Server client (https://github.com/mongodb/mongo/blob/6212e50e73dd032b448a514fe6893c6490a28a9f/src/mongo/db/commands/authentication_commands.cpp#L294-L300),

    Example,
    {"t":{"$date":"2021-05-10T11:08:03.110+0000"},"s":"W", "c":"ACCESS", "id":20430, "ctx":"conn116","msg":"Client isn't a mongod or mongos, but is connecting with a certificate with cluster membership"}

    Proposal,
    * Don't attempt to auth with X.509 certificate from net.tls.clusterFile / net.tls.certificateKeyFile MongoDB Server parameters and use MongoDB Agent X.509 certificate configured.

    Problem Statement,
    What is the problem? MongoDB Agent (Automation Module) attempts to auth with net.tls.clusterFile / net.tls.certificateKeyFile X.509 certificate first, pretending it is a Replica Set member.

    Why is this a problem? MongoDB Server process logs are flooded by unnecessary noise from such MongoDB Agent (Automation Module) auth attempts pretending it is Replica Set member. MongoDB Server will always log Replica Set member auth certificate usage outside of internal MongoDB Server client (https://github.com/mongodb/mongo/blob/6212e50e73dd032b448a514fe6893c6490a28a9f/src/mongo/db/commands/authentication_commands.cpp#L294-L300),

    Example,
    {"t":{"$date":"2021-05-10T11:08:03.110+0000"},"s":"W", "c":"ACCESS", "id":20430, "ctx":"conn116","msg":"Client isn't a mongod or mongos, but is connecting with a certificate with cluster membership"}

    Proposal,
    * Don't attempt to auth… more

    9 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Automation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close