Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Connect Tab in UI should show a replica set (instead of a host) connection string if deployment is a replica set

    I have a 3-node replica set deployment. When I retrieve the connection string to the cluster via OM UI, it shows a single node connection string

    mongo --host ip-10-0-200-4.eu-west-2.compute.internal --port 27017

    I expect it should show a connection string which includes all hostnames, or something equivalent, if deployment is a replica set.

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  2. More fine granular OpsManger roles for API CRUD operations

    More fine granular OpsManger roles for API CRUD operations

    In order to generate API Keys users need some pretty powerful role https://docs.opsmanager.mongodb.com/current/reference/api/org-api-keys/. Same for project API Keys https://docs.opsmanager.mongodb.com/current/reference/api/project-api-keys/.

    Our understanding is that user who can create api keys could also self promote themselves to super admins which is something we don't want and would be a security concern to us. (And admins normally have access to far more things than just user mgmt)

    Additionally it would be beneficial to pass in an desired api key - e.g. for initial provisioning and give admins the chance to reset/rotate an…

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  3. Incorporate Support CASE management into the OPS Manager, i.e. open a case, upload traces to the case etc

    Incorporate Support CASE management into the OPS Manager, i.e. open a case, upload required traces to the case and maybe even automatically create a support case for some critical problems.... Minimally I'd like to be able to upload required traces directly from sevrer(s) using wget/curl functionality and attach the upload files to the existing support case(s).

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add MongoSparkHelper native support for pyspark

    I went through Mongo spark connector python documentation but the thing which I could not find in python documentation was "MongoSpark Helper" section which is available in scala and java documentation.
    I was wondering if there is a way to use it in python code after adding the mongo spark connector packages.

    A sample code to demonstrate what is available and what I am looking for (this code is in scala and I am looking for a similar behavior in python)

    Code in use:
    sparkSession.read.format("mongo").option("uri", "mongodb://dummymongo:27017")

    Code looking for:
    MongoSpark.builder().connector(connectorwithcustomclientfactory)
    .sparkSession(sparkSession).readConfig(dummyReadConfig).build().toDF()

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  5. Enable Ops Manager alerts on any FATAL or ERROR lines in the mongod/mongos logs

    What is the problem that needs to be solved?

    All possible error states and failures reported in the mongod and mongos log files are not raised as alerts in the Ops Manager alerting system. This prevents users from configuring alerts on important events in MongoDB deployments.

    Why is it a problem? (the pain)

    For some users specific errors such as FATAL or ERROR lines in the mongod log need to be alerted and addressed with urgency. Since the specific high priority event is different for different users, a configurable, string matching (regex) driven alerting system that constantly monitors the mongod

    3 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  6. Naming or tagging Ops Manager daily/weekly/monthly/yearly backup snapshots

    Naming or tagging Ops Manager daily/weekly/monthly/yearly backup snapshots

    3 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow configuring Ops Manager to ignore proxy for internal requests

    A very common Enterprise HTTP Proxy configuration is to deny requests from local networks (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).

    In hybrid mode, the Backup Mode attempts to download the binaries from itself locally through the proxy. This brings to errors as the proxy is blocking the local traffic.

    4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  8. Snapshots taken by Ops Manager Backups should include config file

    When restoring a snapshot through Ops Manager, automation will create the config file for you. But if you're restoring a snapshot manually, there's no config file! Surely we can include a sample mongod.conf withe sufficient information filled out to help a user get up and running again.

    5 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow Ops Manager users to move/migrate backup job snapshots from one S3 bucket to a different S3 bucket

    Ops Manager users with S3 blockstores may need to move snapshots and backup jobs to a new S3 bucket. For MongoDB blockstores, this is accomplished using a groom.

    Move Blocks to a Different Blockstore
    https://docs.opsmanager.mongodb.com/current/core/administration-interface/#groom-priority-page

    This feature request is to provide the same feature to groom backup snapshots/jobs to a new bucket for S3 blockstores.

    5 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Backup  ·  Flag idea as inappropriate…  ·  Admin →
  10. Provide recurring/daily reporting on backup status from Ops Manager

    Ops Manager should generate a recurring/daily report of the status of all backups. This report should include at least a list of successful snapshots, a list of unsuccessful snapshots (over the configured reporting period), and the latest successful snapshot for each deployment being backed up. Additionally, this report may include resource availability such as storage available for future snapshots.

    6 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Backup  ·  Flag idea as inappropriate…  ·  Admin →
  11. Ops Mgr "Insufficient oplog size" is confusing and prevents backups

    When using Ops Manager UI (I've not checked the API) to declare a MongoDB cluster to be backed up, Ops Manager tries to be a good citizen and check to see if the clusters oplogs are large enough, based on their recent usage to hold at least 3 hours worth of data based on the last 24 hours of usage patterns. if the check fails, the user is prevented from enabling backup and is shown the warning:

    "Insufficient oplog size: The oplog window must be at least 3 hours over the last 24 hours for all members of replica set…

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  12. Webpage session expiry - introduce inactivity timeout

    Currently one can specify a "Session Max Hours" - The number of hours before a website session expires and a user must login again.
    This should be replaced or enhanced with an "Inactivity timeout".
    We have the requirement to set a timeout due to PCI.
    However with the current implementation I have to re-login to the website even when working actively with OPS Manager. An inactivity timeout would allow to be logged out when I am not working on the OPS Manager, but not whilst working with it.

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  13. In the event of an integrity check job failure, an alert should be shown on Ops manager UI instead of solely relying on email

    Integrity Check Jobs failures get emailed to the configured "mms.backup.alertsEmailAddr" address and logged in daemon.log. This information should also be available in Ops Manager UI so that the user can quickly check before trying any restoration.

    4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Flag idea as inappropriate…  ·  Admin →
  14. Password policy enforcement

    Currently, MongoDB doesn't provide any way to enforce password policies. If there is some way for Ops Manager to enforce a configurable password complexity and age for user accounts managed through Ops Manager, that would be huge win. This can be as simple as adding UI-level validations to the create/edit user form.

    1 vote
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  15. View all clusters grouped by projects (like in Ops Manager)

    There doesn't seem to be an equivalent for Ops Manager All Clusters page in Cloud Manager. It is a good way to quickly glance over all cluster states, stats and versions.
    Can it be added?

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Cloud Manager  ·  Flag idea as inappropriate…  ·  Admin →
  16. Ability to stop/start/restart BI Connector in Ops Manager

    Currently, Ops Manager does not support stop/start/restart BI Connector that is managed by Ops Manager Automation. There is only a Terminate option available.

    4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Automation  ·  Flag idea as inappropriate…  ·  Admin →
  17. mongocli feature request : add an option to specify the path to the CA file in the mongocli configuration.

    Currently while using mongocli to connect to Ops Manager via https, one needs to add the public CA certificate to local system's trusted certificate store. Please add a parameter in the configuration file where one can specify the path to the local CA file

    1 vote
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  18. Cloud Manager should offer Feature Compatibility Version setting for new clusters

    When creating new clusters in Cloud Manager, there isn't an option to create them with a specific FCV. We just had a need to build a 4.2 cluster with FCV 4.0, and had to do it manually while shutting down automation.

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Cloud Manager  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow to configure `maxTimeMS` for commands executed from Ops Manager's Data Explorer

    What is the problem that needs to be solved? Allow to configure maxTimeMS for MongoDB commands which are executed from Ops Manager's Data Explorer.

    Why is it a problem? (the pain) A) Ops Manager's Data Explorer cannot work with [views](https://docs.mongodb.com/manual/core/views/index.html) in case if the view is taking >15000 ms to be load. Data Explorer cannot work with [find](https://docs.mongodb.com/manual/reference/command/find/index.html) operations in case if that find operation is taking >15000 ms to be completed.

    5 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add support for collections with default locale

    At present if a collection has a default collation configured, sharding such a namespace via Ops Manager results in a failure with the following symptom:

    <myCluster_mongos_131> [13:21:17.050] Plan execution failed on step ShardCollections as part of move ShardCollections : <myCluster_mongos_131> [13:21:17.050] Failed to apply action. Result = <nil> : <myCluster_mongos_131> [13:21:17.050] Error calling shardCollection on sh.myColl with key = [[a 1]] : <myCluster_mongos_131> [13:21:14.994] Error executing WithClientFor() for cp=mubuntu:27017 (local=false) connectMode=AutoConnect : <myCluster_mongos_131> [13:21:14.993] Error running command for runCommandWithTimeout(dbName=admin, cmd=[{shardCollection sh.myColl} {key [{a 1}]} {unique false}]) : result={} identityUsed=mms-automation@admin[[MONGODB-CR/SCRAM-SHA-1]][24] : (BadValue) Collection has default collation: collation: { locale: "fr", caseLevel:

    4 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base