Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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.

    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

    2 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add the ability to trigger alerts for testing purposes

    It would be useful to have a "Test Alert" button for each configured alert in order to integrate and test alerts with third-party systems. Otherwise, it is difficult if not impossible to determine what the alert will look like until it is triggered.

    14 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

    1 comment  ·  Monitoring / Alerts  ·  Flag idea as inappropriate…  ·  Admin →
  3. Create Ops Manager API endpoint to download mms0.log files

    We should expand the Ops Manager API to provide mms0.log downloads the same way we allow mongod deployment log downloads. This will help users with diagnostics when they deploy many Ops Manager instances via the kubernetes operator but do not yet have centralized logging.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  4. mongomirror compatibility with SRV strings

    It would be ideal if the mongomirror utility could accept SRV-based connection strings for the source and destination clusters. The inability to do this can cause pain for customers. For example, this does not work:

    --destination "mongodb+srv://mgo-aura-dgs-prdsrv-tk-pl-0.yrmiy.mongodb.net"

    So users are stuck doing this:

    --destination "atlas-nkaylx-shard-0/pl-0-ap-northeast-1.yrmiy.mongodb.net:1036,pl-0-ap-northeast-1.yrmiy.mongodb.net:1037,pl-0-ap-northeast-1.yrmiy.mongodb.net:1038"

    Two issues with that:
    1. It's painful looking up the host/port and atlas defined replica set name
    2. The destination info is unreadable by most humans. The service name (i.e. SRV record connstring) includes the name of the cluster that the customer defined, and not the random has that Atlas generates

    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

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  5. Configure MongoDB Automation Agent collecting stats on some collection to not trigger alerts

    We just had a support case about some alerts being raised on our cluster because the MongoDB Automation Agent collecting stats on some collection doing queries without index triggers "Scanned Objects / Returned" ratio has went over 1000.

    It would be really nice to at least not raise alerts when it's the mongodb automation agent that triggered it. Were monitoring our alerts a lot and these are false positive we can't do anything about it seems other than create all the indexes it needs, which might change over time. We have no guarantee of which index it needs.

    Another alternative…

    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

    1 comment  ·  Automation  ·  Flag idea as inappropriate…  ·  Admin →
  6. Integration with Microsoft Teams

    Add third-party service integration for Microsoft Teams, as we do for Slack.
    Most likely the following can be leveraged to achieve the integration: https://docs.microsoft.com/en-us/graph/teams-proactive-messaging

    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

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

    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 →
  8. Sharded Cluster Snapshot Restores - Throttling and Src/Dst Mapping

    When restoring a sharded cluster snapshot, provide a means of mapping the source shard replica set names to the target shard replica set names. This will allow users to predictably restore large/small shards to the appropriate target hosts.

    Currently, this can be done for sharded clusters with fewer than 10 shards by naming the shards in a predicable shard## pattern. However, greater than ~10 shards leads to an alphabetical => alphanumeric restore plan (e.g. shardA10 restores to shardB2).

    Restoring large sharded clusters can also overwhelm networks where MongoDB Agents are downloading snapshots from Ops Manager(s) at the same time. Please…

    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

    0 comments  ·  Backup  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add support for virtualization volume management in Ops Manager Backup snapshots and restores.

    Streaming snapshots during a restore from a blockstore out to the MongoDB Agent cases the RTO (recovery time objective) to grow linearly with the compressed datasize in the largest shard/RS of the snapshot. The RTO of an Ops Manager restore could be very significantly improved by leveraging volume management infrastructure (such as from VMWare) to restore previously acquired snapshots as virtual filesystems (volumes).

    14 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  ·  Backup  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add the ability for the backup daemon to download and validate snapshots

    In order to test snapshots automatically, create a new job type that allows the Backup Daemon to download the snapshot from the snapshot store, then run validate on each collection.

    If any collection fails validation, send an alert to the Backup Admin with the list of corrupted data.

    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

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  11. Deploy MongoDB across different Kubernetes clusters

    MongoDB Operator can only deploy and manage MongoDB in a single Kubernetes cluster. However, for DR and global apps, it is important to deploy a single DataBase across multiple Kubernetes clusters to allow for DR or globally distributed apps.

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

    We are going to start POC in July to figure this out. Our goal is to form a single cluster that can fallback between different K8S clusters.

  12. Ops Manager and Backup infrastracture Disaster Recovery support with K8s Operator

    We have carried out tests with MongoDB v1.5.5 K8s Operator and Ops Manager 4.2.18 with Backup infrastructure (S3 Snapshots) in an Openshift 3.11 environment (MongoDB Support case attached).

    In this case, a "Disaster Recovery" simulation has been carried out. However, several components created by the Operator had to be restored to obtain a similar state to the one before the "disaster".

    Furthermore, it is very likely that the S3 Snapshots will be lost if the process is not completed in a certain manner.

    It would be great to have an official approach to deploy/restore an OM resource using MongoDB K8s…

    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  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  13. Project Alert Integration With Rocket.Chat

    Integration with Rocket.Chat like done in Slack.

    5 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

    1 comment  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  14. Feature to add the Certificate Authority file to the Ops Manager Java Trust Store via UI

    Currently, Ops Manager user may require to add the CA for the TLS enabled destination such as SMTP Server, on-prem S3, Webhook Endpoint, etc directly to the Java Trust Store. Adding CA to Java Trust Store also requires to re-apply if Ops Manager Application is upgraded or re-install.

    It would be best to have a feature in Ops Manager so that the user is able to upload the required CA via UI.

    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

    1 comment  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  15. add details to alert Query Targeting: Scanned / Returned to identify what triggered it

    If you want to catch full scan on collection you could set up alert "Query Targeting: Scanned / Returned > 1".
    OPS Manager does not provide any details where it was triggered.
    it would be nice to get db/collection/query which caused this issue. Query still can be fast (for example, not many document in collection yet or hardware is idle/fast at the moment) and will not go to slow operation group.

    13 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

    1 comment  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  16. Restore Backup Snapshots to Sharded Clusters via mongos

    Migrating large sharded clusters to a different cluster pre-sharded with different shard keys requires a significant amount of time to balance post-restore.

    This is a feature request to restore a snapshot on a per document basis through a mongos. The desired result is a completed restore with collections/documents residing on their target shards.

    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  ·  Backup  ·  Flag idea as inappropriate…  ·  Admin →
  17. Properties option for a server node

    Up until Ops Manager version 4.0+, we are/were able to view "Properties" of all servers/Replica sets by clicking on the ellipsis option on the each server. But will the latest versions of Ops Manager, that option is no longer available. We are often looking to quickly identify the allocated resources such as CPU/RAM on servers to help troubleshoot and deduct if we need to add more resources, so this has been a helpful feature we have used. We would very much like to see this feature option to be revived in the current versions of Ops Manager 4.2 and 4.4.4.

    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 →
  18. Project template defaults for replica set Attributes

    Our standard replica set deployments require a number of items to be set in the edit/modify area of each replica set...such as:
    sslMode
    directoryPerDB
    directoryForIndexes
    javascriptEnabled
    redactClientLogData

    Since we create hundreds of replica sets the amount of time spent repeatedly setting these attributes, which are considered "default" in our shop, adds up. Having the ability to set a template of defaults per project would save a great deal of time.

    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 →
  19. Only download to /mms/mongodb-releases/ those versions actually in use in a deployment

    /mms/mongodb-releases/ is continually updated with the most current minor release of each major version which can fill the partition.
    This request is for "Only download to /mms/mongodb-releases/ those versions actually in use in a deployment"
    eg if I am only using 4.2.20 in my actual deployments only download the most recent 4.2.x and not 3.6.x
    of course if I do decide to deploy a 3.6.x deployment this FR would need to automatically be bypassed and download my 3.6.x and the most recent 3.6.x.
    This request is similar to but not the same as another Feature Request:
    [Do not download EOL…

    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 →
  20. Add to the Continues Backup UI more information about the snapshots

    Currently, the Ops Manager UI under Continues Backup only shows the following information about the snapshots:
    - Replica set name
    - Status
    - Last Snapshot
    - Last Oplog Slice

    It would be very helpful to also see:
    - Start date/time
    - Finish date/time
    - Backup duration
    - Snapshot size

    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 →
← Previous 1 3 4 5 10 11
  • Don't see your idea?

Feedback and Knowledge Base