Skip to content

Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

469 results found

  1. 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…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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…

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. export & import alerts settings from one project to another project

    export & import alerts settings from one project to another project

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Ability to migrate from Ops Manager to Cloud Manager

    Clearly users of Ops Manager use it because they have a requirement, keep MongoDB clusters within their own infrastructure.

    Well, we have two solutions for that Ops Manager and also Cloud Manager. I personally think if we have automation in the product to move from the Ops Manager control plane to the Cloud Manager control plane it would make it easier for users to take advantage of MongoDB's backup infrastructure and keep updates coming without the hassle of managing it all by themselves.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Ops Manager: add LDAP timeout options

    Our LDAP server is quite slow, so we sometimes get technical errors when trying to log in our Ops Manager instance.

    We would need add an option to set LDAP server response timeout on Ops Manager side. It could be mms.ldap.timeoutMs.

    (I'm refering to Ops Manager authentication, not to MongoDB deployement authentication)

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Ops Manager and attempts to stepDown

    When the majority commit point is not reached, Ops manager should refrain from any config change process like stepDown of a particular primary.

    Sometimes the number of attempts for stepDown can go upto 200 times and the duratio ncould be hours dependign on the data size.

    More details are present in the below ticket:
    https://support.mongodb.com/case/00885173

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Show time it took to complete a snapshot

    In order to better troubleshoot snapshot performance issues, or maintain an understanding of how snapshots are performing and whether one is approaching a threshold where they wont be able to keep up, its a good idea to expose how long a snapshot took in the View All Snapshots page. This would also aid in quickly identifying which snapshots are full vs incremental.

    46 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. The "Get All Network Peering Containers in One Project" endpoint should repo all endpoints regardless of the Public Cloud provider.

    In order to get back the peering list, one has to pass the provider
    shell
    mongocli atlas networking peering list --provider GCP

    This is odd because a) Atlas already knows and b) why not list all the peering regardless of the provider. We cannot specify filters in many cases already like, 'cluster list' and would have to use jq to filter. We can do the same here is folks really want to filter. In other words, in general, please stick to one design maxium, provide all items in the 'list' or provide a way to filter, but not both.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Update MongoDB driver in Elastic metricbeat and validate operability with Atlas

    The metricbeat data collection agent from Elastic currently has a MongoDB module for capturing low level metrics from a MongoDB instance. It's using a very old MongoDB driver that doesn't work with recent versions, nor work with Atlas.

    I realize metricbeat isn't a MongoDB product or supported integration but it seems like it'd be low effort from an experienced Golang developer (which I am not) and remove an impediment from potential requirements around MongoDB metrics having to be captured using company-standard observability solutions. Thanks!

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Ops Manager: Test Failover

    The ability to Test Failover was added to Atlas https://docs.atlas.mongodb.com/tutorial/test-failover.

    Please add this functionality to Ops Manager in order to facilitate failover testing. This is especially useful in multi-tenant Ops Manager setups.

    20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. list who is connected to a cluster

    Hello,

    On a sharded instance, I try to identify the connected physical people.
    It is not easy. I cannot identify my own connection. 😦

    Can we have a command to find out who is connected to the platform (excluding host2host connections, backup process, ...)?

    The closest command but not complete and friendly :
    use config
    DBQuery.shellBatchSize = 300
    db.system.sessions.aggregate( [ { $listSessions: { allUsers: true } },
    { $project: { _id: 0, "user":"$user.name" } } ,
    { $group : { _id: {"user": "$user" }, count: { $sum: 1 } } },

    ])

    Regards
    Jerome

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Allow the use of symlinks within the Ops Manager directory

    Sometimes it would be great if we could move the conf, tmp, or logs directories to other filesystems and use symlinks so that Ops Manager doesn't have to worry about where the needed file physically are. Right now, Ops Manager refuses to start whenever this sort of redirection is done.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base