Skip to content

Ops Tools

← MongoDB Feedback Engine

How can we improve the Operational Tooling MongoDB provides?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

480 results found

  1. 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
    0 comments  ·  Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?

  2. add organisation name to project name when project name is not unique

    There are multiple places where we need choose project. for example, to create global alerts we can exclude some projects from this alert.

    The issue is project name is not unique and there could be projects with the same name in different organisations. For example, every organisation may have project dev or test.

    it comes to the issue that you will see in the list of projects "dev,dev,dev,dev" and you don't understand which one you want to use.

    it will be much better to display them in the format "org/project", so the example above would be "org1/dev, org2/dev, org3/dev" which…

    2 votes
    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

  3. Add options to the connection string through the MongoDBUser

    We would like to add options to the connection string that is generated by the operator when creating a new MongoDBUser.
    The idea is to include these options in the MongoDBUser CRD so the operator can then add them to the connectionString stored in the generated secret.

    1 vote
    1 comment  ·  Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?

  4. 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
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

  5. 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
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

  6. Add a variable for set the RS name

    Add own variable to set the RS name so that the deployment name can be used to name the pod

    1 vote
    0 comments  ·  Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?

  7. allow mongocli read configs from stdin rather than from file

    To deploy new cluster we need prepare config file and put there all sensitive data, like automation user password, ssl cert passwords etc.
    Then we have to specify -f flag to point to this config during mongocli call.

    Currently this file has to persist somewhere on the disk during call to CLI which makes it insecure (and file has to be carefully removed after cli call finished, proper access to the file has to be set etc)

    It would be safer to send this config to stdin of mongocli - as a pipe from another command which can generate the…

    2 votes
    0 comments  ·  MongoDB CLI for Cloud Manager and Ops Manager  ·  Admin →
    How important is this to you?

  8. 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
    2 comments  ·  Monitoring / Alerts  ·  Admin →
    How important is this to you?

  9. Supporting the installation of mongosh in Ops Manager Local Mode

    Ops Manager v6.0+ supports installing the new mongo shell (mongosh) to the deployment nodes. This feature is not supported in Ops Manager Local Mode.

    It would be convenient to the Ops Manager Automation user if they could upload the mongosh binary to the Ops Manager Versions Directory and Ops Manager will install the binary to the deployment nodes similar to the MongoDB Binary and MongoDB Database Tools.

    Currently, the customer with Local Mode needs to manage the installation of mongosh outside of Ops Manager Automation.

    6 votes
    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

  10. Added features to improve backup performance on filesystem

    Currently, the ability to use multiple workers in Ops Manager is only available for S3. If possible adding this capability, or additional enhancements, to filesystem storage would be beneficial.

    1 vote
    0 comments  ·  Backup  ·  Admin →
    How important is this to you?

  11. Backup Daemon should check for the available filesystem before starting a groom job

    When a groom job starts, it might get stuck or fail if the available disk space is not enough to copy all live blocks to another directory.

    It would be helpful if the Backup Daemon checks the available disk space before starting a groom job, and notifies the user:
    1. via Ops Manager UI
    2. report it in the logs
    3. sends an alert that the upcoming/scheduled groom job would not start due to low disk space.

    6 votes
    0 comments  ·  Backup  ·  Admin →
    How important is this to you?

  12. monitoring opt

    Allow to configure startupOptions for monitoring/backup agent logs in yaml for deployments. Similar as we have for AppDB - spec.applicationDatabase.monitoringAgent.startupOptions

    4 votes
    1 comment  ·  Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?

  13. clear text password for mongodb ldap authorization

    Add the feature to Encrypt the queryPassword parameter for LDAP in the config file directly via Ops Manager , so that text password should not be present in config file.
    Keeping direct password is a security concern.
    Sample format of the config file:

    ldap:
    authz:
    queryTemplate: '{USER}?memberOf?base'
    bind:
    method: simple
    queryPassword: <Password>
    queryUser: <username>
    servers: serevername:port
    transportSecurity: tls
    userToDNMapping: '[ { match : "xxxxx)))"
    } ]

    4 votes
    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

  14. Ops Manager should allow to perform restore/recovery on individual replica node

    Currently Ops manager automatic restore process does not support restoring snapshots to a single node of a existing replicaSet instead Ops Manager restore snapshots to an existing replicaSet.
    This will be require in case any individual replica node down for longer period and oplog overwrite on primary.
    Thank You

    1 vote
    0 comments  ·  Backup  ·  Admin →
    How important is this to you?

  15. 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
    2 comments  ·  Other  ·  Admin →
    How important is this to you?

  16. Enable external-dns integration via per-service annotations on each generated service

    Currently the MongoDB Kubernetes Operator allows specification of annotations on services created by the operator, but only annotations with the same value across all services. The external-dns operator can create DNS names based on annotations on services. In order to support external-dns integration the MongoDB Kubernetes Operator would need to allow one to specify specific annotations for each generated service.

    Current spec for external access services:
    externalAccess:
    externalService:
    annotations:
    # Same annotations will be applied on all services

    You could consider a placeholder/substitution scheme like:
    externalAccess:
    externalService:
    annotations:
    external-dns.alpha.kubernetes.io/hostname: mydb-db-<instance number>.mydns.com

    Or some other way of assigning a per-service annotation…

    1 vote
    0 comments  ·  Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?

  17. Set log file permissions using Ops Manager

    Currently there is no way to set the log file permissions from Ops Manager and the default value is 600. Our organization uses Splunk and with the current settings the Splunk user is not able to read the log files. Config file options such as processUmask and honorSystemUmask can be used to change the log file permissions, but they will also change other files such as journal files, wiredtiger files, etc. The only option we have is to add the Splunk user to our role group in Unix, but this causes a security issue.

    1 vote
    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

  18. Allow drag-and-drop of metric graphs from different replica set members

    Our use case is we have a replica set, but the east nodes and west nodes are on disk mounts with different names, so they won't appear on the same line in the Metrics tab. We should be able to drag and drop on a replica set member level, not just the metrics level. This allows more customization of metric graph layout.

    2 votes
    0 comments  ·  Monitoring / Alerts  ·  Admin →
    How important is this to you?

  19. OPS Manager should call updateUser to change password to trace it in DB Audit.

    If you enable auditing in database, you can't trace change password actions. The reason is OPS Manager updates system.user collection record directly. as a result, this action is not traceble in audit if parameter auditAuthorizationSuccess is not enabled.

    But enabling this parameter cause performance degradation as all DML/DDL will be sent through audit layer.

    Dropping user at the same time happening as expected and traceable in audit files.

    2 votes
    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

  20. Agent authentication to opsmanager using x509 credentials

    Similar to how Opsmanger can use x509 to manage deployments, it should be possible to configure the agents to use x509 credentials to communicate with Opsmanager. This will allow for a more consistent security posture across the whole mongodb/opsmanager stack. It would also simplify security procedures such as credential rotation by unifying the authentication mechanism.

    This will be an alternative to the existing API Key approach https://www.mongodb.com/docs/ops-manager/current/tutorial/manage-agent-api-key/index.html

    1 vote
    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?
1 2 4 6 … 23 24
  • Don't see your idea?

Ops Tools

Categories

Feedback and Knowledge Base

(thinking…)