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. Separeted mongod and mongodb agent in Kubernetes Operator container

    Now both mongod and agent Ops Manager are running in the mongodb-enterprise-database container. Sometimes it becomes necessary to restart the agent separately from the mongodb instance. Now this is impossible to do because systemd does not work in containers

    1 vote
    0 comments  ·  Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?
    planned  ·  AdminDan (Admin, MongoDB) responded

    We have plans to have the two run separately! Though no firm timeline yet, we're hoping this year.


    Right now we have two architectures. The default is a single container that pulls the binaries for the agent and MongoDB server (mongod) from Ops Manager/Cloud Manager. The other is in Private Preview (potential for breaking changes still) and is known as our Static Architecture.


    Neither actually runs each in their own containers, and we're hoping to alter the static architecture to make that the case before we release it fully and make it the default.


    Aside from restarting one and not the other, this would offer a more intuitive setup when configuring and troubleshooting, and align to a very future proof definition of what "static" means - where security tools are converging on blocking any significant changes to a container between the image and runtime.

  2. deployment metadata resync

    Ops Manager needs a way to resync deployments' metadata from the console (or command line, or API), rather than direct undocumented CURD operations in AppDB.

    My reason for this suggestion:
    See Case: 01438273. One of my deployments had duplicate entries for all 3 nodes. We suspect that happened because we were initially using short name hostnames in the deployment's replica set definition and later changed that to FQDN hostnames. The original entries should have been removed from the AppDB collection, but instead they remained there indicating version 4.0.26, while new ones were created, which were then successively updated as the…

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

  3. we have an ask to use 4 in snapshotIntervalHours

    For the api - https://www.mongodb.com/docs/ops-manager/current/reference/api/backup/update-one-snapshot-schedule-by-cluster-id/ we have an ask to use 4 in snapshotIntervalHours. Right now its not supported. Supported ones are - 6, 8, 12, or 24.

    Please check and let us know if its possible to add 4 as well to the snapshotIntervalHours

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

  4. adding comments directly during the Review and Deploy process in mongo

    Ops Manager currently does not support adding comments directly during the Review and Deploy process.It is essential to add comments in production environments related deployments to keep track of artifacts (such as incident number or change number) to figure out why the change has been deployed.

    Kindly consider adding comments section in review and deployment workflow in ops manager to make ops manager deployments much clear and to have substantial information pon why that deployment is done.

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

  5. For Mongosync add ability to select write concern.

    For Mongosync add ability to select write concern. Especially something along the "all" nodes would be important. Also "custom" one like MultipleDC etc.

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

  6. Automatically move HEADS in case of backup daemon problem

    In configuration with multiply daemons in case of daemon problem (down) switch to another one automatically with restart backup upon need.

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

  7. Warn when trying to apply changes that are doomed to fail

    Ops Manager UI should show a warning when trying to publish changes while a node is disabled (shut down).

    Why ? See this example:
    - user publishes a change asking for node 1 to be disabled
    - publication is OK, node 1 is stopped by Ops Manager
    - user publishes a change asking for node 2 to restart. Ops Manager UI accepts this change...
    - ...but publication will fail, with node 2 agent waiting indefinitely for node 1 to get healthy

    This is really disturbing because Ops Manger accepts a change it knows it can't deliver.

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

  8. Different networks support in Ops Manager

    We need Ops Manager being able to manage our infrastructure architecture.

    We have a service network and an operational network. The servers, at the physical level, are located in the operational network with their domain (for example servername.operational.network.net, which is what is in /etc/hosts and what you get when you run "hostname -f") and the replica set nodes, at the MongoDB level, are in the service network (for example servername.service.network.net).

    When you try to add an existing MongoDB deployment in Ops Manager, as indicated in the wizard, you must do it with the name…

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

  9. Operator opsManager.configMapRef as a secret

    currently inside the mongodb Operator custom resource MongoDB, a configMap stores the orgId.
    e.g.

    apiVersion: mongodb.com/v1
    kind: MongoDB
    metadata:
    name: my-mongodb
    spec:
    ...
    opsManager:
    configMapRef:
    name: my-mongodb-ops-manager-diga-project-configmap
    credentials: my-mongodb-opsmanager

    please allow storing the orgID inside a secret via:

    spec:
    ...
    opsManager:
    secretRef:
    name: my-mongodb-ops-manager-diga-project-secret
    credentials: my-mongodb-opsmanager
    `

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

  10. Add support in homebrew for mongosync

    Could you add support in https://github.com/mongodb/homebrew-brew for mongosync https://www.mongodb.com/try/download/mongosync

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

  11. Allow OPS Manager to export as CSV or JSON All projects page information

    All projects page in MongoOPS shows cluster name, data size, version, nodes, backup, SSL, Auth, Alerts.

    Add export as CSV or JSON All projects page information.

    Current MongoDB Usage report doesn't fit due:
    1. It doesn't report backup, encryption information
    2. Cluster name could be not right if the cluster was unmanaged and added back to OPS manager as managed. (Cluster_0 bogus names)

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

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

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

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

  15. Allow optional email notifications for OpsManager monitoring rule changes due to security concerns.

    1 vote
    0 comments  ·  Monitoring / Alerts  ·  Admin →
    How important is this to you?

  16. 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
    0 comments  ·  MongoDB CLI for Cloud Manager and Ops Manager  ·  Admin →
    How important is this to you?

  17. 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
    0 comments  ·  Enterprise Kubernetes Operator  ·  Admin →
    How important is this to you?
    under review  ·  AdminDan (Admin, MongoDB) responded

    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.

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

  19. Allow configuring external applicationDatabase running on MongoDB Atlas

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

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

  20. 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
    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?
1 2 … 14 16 18 … 23 24
  • Don't see your idea?

Ops Tools

Categories

Feedback and Knowledge Base

(thinking…)