Skip to content

Ops Tools

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

469 results found

  1. Allow conditions for all alerts based on DB/cluster name

    We have a need to route alerts based on our database/cluster's impacted instead of having them apply to any in the current project. I know some of them can condition based on host name, which uses the cluster name, but most alert types have no similar option.

    Examples would be:
    Search Index Build Complete
    Search Index Build Failed

    These are sent without conditions and even the message does not indicate what cluster they are for (although you can guess based on the collection name provided).

    We do not have the option to route these ourselves with a webhook, as the…

    8 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)
  2. mongosync filtered sync update

    Currently we cannot modify a filter that is in use without wiping all user data in the target cluster.
    For exclusion filters, where we exclude collections NOT to copy, adding more collections to exclude should not require wiping all user data.
    This is very cumbersome otherwise.

    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)
  3. Show better diff for changes to setParameter json blob

    The "review and deploy" step only shows that there IS a diff in the setParameter json, but it does not make it clear what is actually changing.

    It would be very helpful to show the diff between the two json payloads in an easy-to-read way.

    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)
  4. The Backup Daemon auto downloads all old Mongodb versions

    If "Backup Versions Auto Download" is set to true on the Admin > General > Ops Manager Config > MISCELLANEOUS tab, then the backup daemon automatically downloads all older major versions of the software.
    In my opinion, it would be better if you could either select the version/s which you want or it only downloaded versions equal to or higher than your current version.
    All the old versions take up disk space and can only be deleted if the setting is changed to false.
    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

    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)
  5. Add support to convert a replica set to a sharded cluster in Kubernetes

    Currently it is not possible to use Ops Manager UI or Kubernetes Operator to convert Replica Set to Sharded cluster. Error : changed not allowed.

    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)

    Planned - we have a requirement to have this completed in time for MongoDB 9.0. But no timeline (yet) for delivering this within that timeframe. 

  6. Mongo Atlas: create backup before updating version

    If I upgrade Atlas cluster, Atlas automatically creates a backup with the new version.
    I'd rather have a backup of the cluster with original version.
    It will allow to restore to the previous version.
    Current workaround: create a backup manually before upgrade.

    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)
  7. encryption at rest

    Right now there is only option to encrypt the key used to encrypt the database. There is no way we can choose which encryption technology is being used to encrypting the database and its backups. The default protocol being used by mongodb may not align with the security policy of the company.

    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  ·  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)
  8. 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)
  9. Improve Enterprise Kubernetes Operator PVC expansion

    The enterprise operator should be capable of performing all the steps necessary to increase the PVC after the end-user has adjusted the storage values within the MongoDB custom resource.

    Reference:
    https://www.mongodb.com/docs/kubernetes-operator/stable/tutorial/resize-pv-storage/

    Why is the Operator incapable of doing the steps starting from step 3 by itself if I simply do step 5?

    So what we think should be the case:

    We update the database resource with a new storage value.

    Then should perform the following steps:

    • Patch each persistence volume which can be found in the sts / pod spec.
    • Remove the sts with --orphan because the name should be…
    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. mongoimport should explain why documents fail schema validation

    Currently, with mongoimport 100.9 and MongoDB 7.0 with schema validation enabled, mongoimport will only report that a document failed to import due to schema validation. It would be useful if it could explain why it violates the schema (e.g. which fields are missing, which datatypes are incorrect, etc.). This is similar to the feature request for MongoDB Compass2

    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)
  11. Operator crashes when it doesn't have permissions to watch a namespace

    If one of many namespaces does not set the permissions for the operator to watch the namespace, it throws exceptions and goes to crashLoopBackOff state.
    This is clearly a bug. One misconfigured namespace should never be able to take the operator down with it.

    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)

    This is expected behavior and common among operators; it can't function and do what's needed if it lacks the permissions needed.


    I know we have an open support case around this to try and understand more about your use case, and we're hoping that we'll be able to offer some guidance to avoid this problem and still achieve what you need. It may even be a new use case that we look to support.

  12. Make all metrics used in the Atlas dashboard available for the prometheus integration

    Make all metrics used in the Atlas dashboard available for the prometheus integration (https://www.mongodb.com/docs/cloud-manager/tutorial/prometheus-integration/#mongodb-metric-labels).
    Also describe how the current Atlas dashboard metrics are build from those.
    I'm looking especially for the metrics:
    - Max Disk IOPS
    - Queues

    6 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. Allow assigning users to an organization via api by adding a bypass parameter

    Via the parameter bypassInviteForExistingUsers it is possible to a add a user to a project.
    It is important to also have this feature for the Organization, so please add a parameter bypassOrgInviteForExistingUser or similar to enable this.
    Without it, we can not automate the creation of new environments.

    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)
  14. Allow configuring external applicationDatabase running on MongoDB Atlas

    Allow configuring external applicationDatabase running outside of Kubernetes in the opsManager configuration.

    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)
  15. Add Public API Endpoint for Backup Snapshot Status

    When a snapshot is ongoing, the only location to find information on the current status is in the UI on the backup page for a project.

    An API endpoint with the same information as the UI would allow for automation and alerting tools if the snapshot creation is not performing as expected.

    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)
  16. Management capabilities for trusted CA certificates in the Admin UI

    Currently it is a manual process per Ops Manager server to add trusted CA certificates to the Java TrustStore. This store is also overwritten on Ops Manager upgrades.

    Similar to the S3 block store option to use a specific CA, it would be useful to manage trusted CA certificates for other endpoints such as HTTPS proxies, webhook alerts, and custom download URLs.

    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)
  17. Need an alert for KMIP master key rotation

    Currently opsmanager has manual rotation of KMIP master keys.

    Enhancement required:
    Need an alert from project level to rotate keys when nearing the schedule rotation just like SSL expiration alerts

    Need for automation of this key rotation would be helpful. If fails, it needs to revert back changes and alert for human intervention.

    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)
  18. Add support for zstd compression in Ops Manager connection string

    I just tried to enable zstd on the mongo.mongoUri connection string for Ops Manager and it looks like it's not supported

    Feb 6 13:53:20 opsmanager1 mongodb-mms[3971104]: An unexpected error occurred during pre-flight checks: com/github/luben/zstd/ZstdInputStream
    Feb 6 13:53:20 opsmanager1 mongodb-mms[3971104]: java.lang.NoClassDefFoundError: com/github/luben/zstd/ZstdInputStream

    Given the high network in/out values we see from the mongo underlying Ops Manager, I think zstd is likely to be very effective and helpful!

    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)
  19. Add an option to GUI to rotate Certificates

    Add an option to GUI to rotate Certificates for each or all instances of replicaset for MongoDB.

    Should include options:

    1) rotate certificates for one instances on one server.
    2) rotate certificates for all instances belonging to a replicaset.
    3) rotate certificates for all instances on one server.
    4) rotate certificates for all instances on all servers for a project.

    Similar to https://www.mongodb.com/docs/manual/reference/command/rotateCertificates/#mongodb-dbcommand-dbcmd.rotateCertificates

    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  ·  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 service spec changes via MongoDBCommunity CR

    I aim to include extra sidecar containers, such as a metrics sidecar, allowing me to deploy an external metrics exporter alongside that would be scraped via service. I intend to configure annotations on the service for Prometheus automatic discovery, enabling the scraping of metrics and exposing the exporter container at the service level, similar to the one exposed when prometheus integration is enabled.

    Updating the service spec is not currently possible, and as result, a lot of manual steps are required, like creating a custom service for each cluster, which points to the sidecar container with the required annotations in…

    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)
  • Don't see your idea?

Feedback and Knowledge Base