Skip to content

Ops Tools

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

436 results found

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

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

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

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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.

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

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

    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

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

    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)
  8. 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)))"
    } ]

    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  ·  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. 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

    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)
  10. 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)
  11. 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

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

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

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

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

    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. Use Custom S3 buckets for backup storage on cloud manager

    Requesting new functionality to be able to use a custom S3 bucket to store backups taken from cloud manager.

    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)
  17. Providing a grafana dashboard for an on-premise cluster

    It would be interesting to provide a grafana dashboard when integrating with prometheus.

    The documentation is indeed very limited concerning metrics when you're on a mongoDB on premise cluster.

    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)
  18. Ability to remove parameter tlsCertificateKeyFilePassword from Advanced configuration

    Currently the behavior around this parameter is tricky -once you added this parameter to advanced config - you can't remove it. if you try to remove it - OPS Manager simply ignores this action and when you run "Review and Deploy" - it displays nothing but still let you deploy this "nothing". similar if you want to set the value of this parameter to empty string from something - OPS Manager ignores it and deploy empty list of actions.

    the workaround is to remove both tlsCertificateKeyFile and tlsCertificateKeyFilePassword in advanced config, but don't deploy it. then add back tlsCertificateKeyFile parameter…

    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)
  19. add clusterId to json output of "cluster list", "cluster describe" commands

    currently there is no straightforward way to get clusterId using mongocli. we can get clusterId if we use text format with "cluster list", but not with json.

    and with json format we have to use "process list" command, filter out only one process amongst multiple within cluster and filter out clusterId.

    it would be useful to add clusterId field into json when we get cluster description from list/describe commands also.

    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)
  20. add text option to --output modifier

    currently there is no way to format output of command in text format. the only option is to set this format as default in config file and not use --output modifier in specific command. if you rare use text output, you will have to insert --output json in every other commands.

    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