Skip to content

Ops Tools

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

31 results found

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

    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)
  3. Ability to export/import index definition from mongoexport/mongoimport and/or mongodump/mongorestore

    Mongodump/mongorestore and/or mongoexport/mongoimport (whichever makes more sense) should provide an option to export/import only indexes. This would aid in non-conventional migration approaches, moving data to lower environments, etc.

    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)
  4. Instantly Release Storage of collection after Remove the data from the collection

    It should provide an attribute when removing a document, inquiring whether you want to release storage immediately or later, instead of executing the compact command. This feature is helpful when you want to retain only the latest 6 months of data and remove older records. For example, I have IoT devices that fetch vehicle GPS locations, and each device has its own separate collection in MongoDB.

    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. Add Health Endpoint to Mongosync

    Mongosync is a constant running process with an API. Please add a /health endpoint for Kubernetes liveness and readyness probes.

    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

    2 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)
  6. Examples for installing operator declaratively on argocd

    Hey there,

    Would it be possible to add some examples when it comes to deploying the community operator with argocd?

    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  ·  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)
  7. mongotop improvements

    Hi. I want to suggest a couple of improvements for mongotop.

    • count output in a grid view. Now only time is supported. Could be implemented with a command line flag
    • limit the number of rows in a grid view with a command line flag (now 10 is hardcoded)
    • pretty print of JSON (by flag)
    • rename parameter rowcount to itercount
    • date pretty print, something more human-readable than ISO format
    • collect more granular stats from the top command. Now we only collect total and locks, * while we can insert, remove, update, etc.

    I could implement them if the improvements are considered…

    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. multi region support for MongoDB Community Operator

    multi region support for MongoDB Community Operator

    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)
  9. Mongoimport CSV columnsHaveTypes to support ObjectID type

    Mongoimport supports a number of import types via the --columnsHaveTypes switch. It would be great if 'objectid' was added as a type.

    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)
  10. mongoimport: trap SIGUSR1 to flush buffer

    If mongoimport is run in the background as a daemon, the user doesn't have many good ways to manually flush the buffer from a scripting standpoint. By default mongoimport flushed data every 1000 documents.

    This feature as already requested at https://jira.mongodb.org/browse/TOOLS-2773 but was closed. I still have the hope that it will be introduced somewhere in future release.

    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)
  11. Release Cadence to allow pegging Minor Version Upgrades prior to GA of next Major Release

    Issue:
    Current requirement to enable 'auto upgrades' to test and take advantage of Minor version updates (Example: 6.x.x >> 6.y.x). As a larger company with a 2-4 week release cycle in our products, we have seen need to start testing a Minor version upgrade to the current Major GA Release (Recent example below).

    Scenario where this could be a problem in summary (See detailed real world story further down):
    - Customer sees a new feature they wish to try.
    - Customer is pegged to last major version upgrade (currently 6.0.x) to allow for pegging the version in production
    - Customer…

    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)
  12. MongoDB Tools Apple Silicon native version

    6.0 now has a native release for Apple Silicon, but the tools are still compiled for x86_64. The https://github.com/mongodb/mongo-tools/blob/master/PLATFORMSUPPORT.md seems to point towards new platform support on internal systems like https://evergreen.mongodb.com/distros - can we get a native build of the tools ?

    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)
  13. 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)
  14. mongocli output text format not displaying all information

    mongocli output text format not displaying all information where as json format dispalying all, if text can display same information as in Json. Will be helpful in updating the alerts etc.

    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)
  15. CRUD Operations history

    We have many number of API/Micro service teams to consume the Mongodb for the data feeding. Sometimes, they ask the CRUD(Insert/Update/Delete queries , not the payload and actual data) history they performed in past. I don't see any option in mongodb how to retrieve those details?

    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)
  16. Add two more entries to the sample_training.zips collections

    The lab task currently can be solved without paying attention to the difference between the $lt vs $lte and $gt vs $gte operators:

    MongoDB Enterprise atlas-7ooiae-shard-0:PRIMARY> db.zips.find({"pop" : { $gte: 5000,$lte: 1000000}}).count()
    11193
    MongoDB Enterprise atlas-7ooiae-shard-0:PRIMARY> db.zips.find({"pop" : { $gt: 5000,$lt: 1000000}}).count()
    11193

    Adding two more documents (one with 5000 and the other one with 1000000 "pop" value) would draw attention to this difference

    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)
  17. mongo push

    Why doesn't MongoDB provide a tool (integrated or standalone) to operate document migration across on-prem (sharded) clusters? Suggestion might be to officially support tools like "mongo push", which may cover situations of hardware changes, production servers migration, re-sharding.

    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  ·  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)
  18. 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)
  19. 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  ·  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. Support for cPanel

    Cpanel doesn't have any support for 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  ·  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)
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base