Skip to content

Ops Tools

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

393 results found

  1. Add addition authentication mechanisms to the Ops Manager Alerting webhook

    Capability to use JWT or SSL certs would be great.

    7 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  ·  Flag idea as inappropriate…  ·  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. Multiple webhook URLs

    At the moment only one webhook URL can be configured for one Ops Manager project.
    It would be nice if multiple URLs could be used to send the alert to different endpoints by using f.e. a delimiter character inside the config.
    Thanks and regards

    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  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Ops Manager to be able to do archiving of Data to a different replica set than you Prod replica set.

    To be able to set up Archiving in Ops Manager so you would be able to keep a certain amount of data in Prod and move the rest of to an Archiving replica set.

    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  ·  Flag idea as inappropriate…  ·  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. 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

    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  ·  Flag idea as inappropriate…  ·  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. 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

    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  ·  Cloud Manager  ·  Flag idea as inappropriate…  ·  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. 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,…

    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  ·  Monitoring / Alerts  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Add command for suspending automation

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

    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)
  8. Allow MongoDBUser CRD to interact with a MongoDB resource in a seperate namespace

    Allow MongoDBUser CRD to interact with a MongoDB resource in a separate namespace in k8s.

    The goal is to have different teams deploy their resources (including applications, configmaps, secrets, PVCs, MongoDBUser CRDs etc) into their seperate namespaces, but have all of them share a single MongoDB replicaset in a common namespace such as mongodb

    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  ·  Flag idea as inappropriate…  ·  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. 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.

    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

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  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. 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…

    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  ·  Flag idea as inappropriate…  ·  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. 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  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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)
  13. 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  ·  Flag idea as inappropriate…  ·  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. 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  ·  Flag idea as inappropriate…  ·  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. 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

    0 comments  ·  Monitoring / Alerts  ·  Flag idea as inappropriate…  ·  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. 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)
  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

    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  ·  Flag idea as inappropriate…  ·  Admin →
    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 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  ·  Flag idea as inappropriate…  ·  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. 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…

    9 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  ·  Flag idea as inappropriate…  ·  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. 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  ·  Flag idea as inappropriate…  ·  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