237 results found

1. Add Global MongoDB Agent Upgrade ability

   Add the ability to upgrade all MongoDB Agents across all Projects at the same time instead of clicking on the banner for each Project.

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   under review  ·  Andrey responded

   We are going to expose this via mongocli first as it would probably makes a fastest solution.

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

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. custom defined roles In OPS Manager

   We need a custom defined role to perform specific functions in the OPS Manager.

   For Example --> We need a custom defined role which can perform subset of functions from Project Automation Admin Role + Project Read Only Role + rs.stepDown() functionality

   Project Automation Admin Role:

   View deployments.
   Provision machines.
   Edit configuration files.
   Download the MongoDB Agent.
   + Project Read Only role.

   Project Read Only Role:

   Activity
   Operational data
   Ops Manager Users
   Ops Manager User roles.

   ** This feature becomes very useful to contain the access of certain privileges and to have the flexibility tailormade privileges instead of giving the access to entire system defined role.

   We need a custom defined role to perform specific functions in the OPS Manager.

   For Example --> We need a custom defined role which can perform subset of functions from Project Automation Admin Role + Project Read Only Role + rs.stepDown() functionality

   Project Automation Admin Role:

   View deployments.
   Provision machines.
   Edit configuration files.
   Download the MongoDB Agent.
   + Project Read Only role.

   Project Read Only Role:

   Activity
   Operational data
   Ops Manager Users
   Ops Manager User roles.

   ** This feature becomes very useful to contain the access of certain privileges and to have the flexibility tailormade privileges instead of giving the… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. trigger a queryable Backup Snapshot restore via Ops Manager public API

   We would like to periodically provision queryable snapshots on a programmatic basis (aka Ops Manager public API call) to easily get a consistent dump of sharded clusters in order to put those dumps in a "very safe location". We want to use this as part of a last resort backup strategy. The idea is that a dump is much easier to be restored by a "last resort restore app" compared to the http-downloaded plain data files.

   One other option to extract the contents of a sharded cluster would be to use "Long Running Queries" but this cannot be used along with mongodump.

   We would like to periodically provision queryable snapshots on a programmatic basis (aka Ops Manager public API call) to easily get a consistent dump of sharded clusters in order to put those dumps in a "very safe location". We want to use this as part of a last resort backup strategy. The idea is that a dump is much easier to be restored by a "last resort restore app" compared to the http-downloaded plain data files.

   One other option to extract the contents of a sharded cluster would be to use "Long Running Queries" but this cannot be used along… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Loadbalance functionality for Ops Manager

   When Ops Manager is under heavy load from many active database services, f.e. to handle backup snapshots, the recommendation from the case support portal is to use a loadbalancer in front of Ops Manager.
   It would be great, if Ops Manager could have this as an integrated functionality to forward connections from agents to additional Ops Manager instances.
   Background: Our nTSE did confirm, that we could set a different Ops Manager URL in the agent config, but the transferred data from this agent is still sent to the initially configured Ops Manager instance.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Reset duplicates button for Ops Manager Admin System overview page

   Sometimes customer want to clean up the System Overview page and/or the application db from because:
   - They dismissed one or more Ops Manager server running Application servers or backup daemon components
   - Their hostnames / domains have changed over the time
   - Their hostnames have changed from lowercase to capital letters or vice versa because upgrading Ops Manager brought a JVM providing different values for getHostname() (this happens often in Windows environment).

   It would be nice to have a button or at least an API call similar to the project reset duplicates that forces Ops Manager to refresh the internal host mappings and the appstate.

   Sometimes customer want to clean up the System Overview page and/or the application db from because:
   - They dismissed one or more Ops Manager server running Application servers or backup daemon components
   - Their hostnames / domains have changed over the time
   - Their hostnames have changed from lowercase to capital letters or vice versa because upgrading Ops Manager brought a JVM providing different values for getHostname() (this happens often in Windows environment).

   It would be nice to have a button or at least an API call similar to the project reset duplicates that forces Ops Manager to refresh the… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. index review before sharding with OPS Manager

   Currently, when you use OPS Manager to shard a collection, it automatically creates a foreground index that exactly matches the sharding key, when such index doesn't exist. When the sharding key column(s) is(are)already prefixing an existing index, it's not sufficent.
   This is dangerous in Live environments because the whole database is blocked for a long time (sharded collections are usually big collections).
   So, several features could exist :
   - before continuing with sharding, OPS Manager warns that it needs to create this foreground index first. You can stop if you don't agree (and create this index by yourself first).
   - OPS Manager creates instead a background index or creates this index with the rolling manner.
   - OPS Manager is able to use one exiting indexes that contains the sharding key as a prefix of this index, no need to create a new one.

   Currently, when you use OPS Manager to shard a collection, it automatically creates a foreground index that exactly matches the sharding key, when such index doesn't exist. When the sharding key column(s) is(are)already prefixing an existing index, it's not sufficent.
   This is dangerous in Live environments because the whole database is blocked for a long time (sharded collections are usually big collections).
   So, several features could exist :
   - before continuing with sharding, OPS Manager warns that it needs to create this foreground index first. You can stop if you don't agree (and create this index by yourself first).
   -… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Project Alert Integration With Rocket.Chat

   Integration with Rocket.Chat like done in Slack.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Add 4.4 tool to PATH

   Since MongoDB 4.4 the tools are located in another folder that is not included in the automation agent bash profile:

   [root@n1 mongodb-mms-automation]# cat /etc/profile.d/mongodb-mms-automation-agent.sh
   export PATH=/var/lib/mongodb-mms-automation/bin:${PATH}

   Would be nice to have also the mongo tools in the path

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Support __exec setting for the MongoDB deployment in Automation

    The deployment that utilizes __exec setting is unable to import to Automation as well as it is unable to deploy the deployment by Automation with this setting.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Binaries should be provided via Docker images

    To implement this in a Kubernetes native way for offline deployments, the binaries should be provided as Docker images and distributed through the Docker repositories that are already present in the k8s environment.

    Option 1 (intermediate): Allow Mount of Docker images in the MongoDBOpsManager resource for the path defined in automation.versions.directory. This would allow us to pre-package the binaries needed and bring up the OpsManager in a kubernetes native way. Everything else (e.g. agent downloading the tgz) would stay the same and still be the "OpsManger-way".

    Option 2 (long term): The MongoDB TGZ package is provided as Docker image by MongoDB (e.g. quay.io). Versioning would be done using tags. These Docker images are then mounted as volume to the MongoDB pod

    To implement this in a Kubernetes native way for offline deployments, the binaries should be provided as Docker images and distributed through the Docker repositories that are already present in the k8s environment.

    Option 1 (intermediate): Allow Mount of Docker images in the MongoDBOpsManager resource for the path defined in automation.versions.directory. This would allow us to pre-package the binaries needed and bring up the OpsManager in a kubernetes native way. Everything else (e.g. agent downloading the tgz) would stay the same and still be the "OpsManger-way".

    Option 2 (long term): The MongoDB TGZ package is provided as Docker image by… more

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    started  ·  1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Periodically notify users of unused versions located in versions directory

    As a safety measure for admins in Ops Manager to avoid facing issues due to unnecessary disk occupation under the Ops Manager installation directory:

    Send periodic notifications (configurable) i.e: once a month; to notify what binaries are not being used by none of the components in their environment so they can evaluate to delete them in order to free up space on their Ops Manager servers.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. restore

    it would be useful to have directly in OpsManager the ability to restore a single database from shapshot.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Opsmanager API: Include Backup Id in List Restore Jobs Response that restore was triggered for

    Hello,

    there is already a snapshot id included in the list restore jobs response, BUT the problem arises with sharded instances: If you restore a sharded instance to a specific backup, multiple restore jobs are created (one for config server, one for each shard). Thus, the snapshot id in the list restore jobs response refers to the backup of the single component (either config server or shard) and not to the overall backup of the entire sharded instance the restore was initiated for.

    Hence, you cannot map those restore jobs to the backup the restore was triggered for, which makes it difficult for us to display the status of the overall restore.

    Suggestion: Add to the list restore jobs response the backup id the restore was initiated with.

    Related support ticket: https://support.mongodb.com/case/01394151

    Thanks for reading!

    Hello,

    there is already a snapshot id included in the list restore jobs response, BUT the problem arises with sharded instances: If you restore a sharded instance to a specific backup, multiple restore jobs are created (one for config server, one for each shard). Thus, the snapshot id in the list restore jobs response refers to the backup of the single component (either config server or shard) and not to the overall backup of the entire sharded instance the restore was initiated for.

    Hence, you cannot map those restore jobs to the backup the restore was triggered for, which makes… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Identify the snapshot of each project and its size in S3 blockstore

    Calculating the storage size consumed by snapshots for each projects deployments for the storage size consumed individually in S3 Blockstore. However, on the S3 snapshot store the data will be stored in the below format which doesn't include any project id to identify the specific project.
    s3://bucket_name/0E3AA1971D5CF1CA52F9AF22A4228F10293AE9804D43FBF7EB5DDE38DB06B74A/5b27b0e4083826088f259f28_A s3://bucket_name/1860B12165FB7ED336DDAB9D306EF38E18FCBD36BF695904C497B825F83581DC/5b27b0e4083826088f259f28_A

    This feature is helpful for the customers to understand and segregate the storage consumption by each deployments

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Add an option to GUI to rotate Certificates

    Add an option to GUI to rotate Certificates for each or all instances of replicaset for MongoDB.

    Should include options:

    1) rotate certificates for one instances on one server.
    2) rotate certificates for all instances belonging to a replicaset.
    3) rotate certificates for all instances on one server.
    4) rotate certificates for all instances on all servers for a project.

    Similar to https://www.mongodb.com/docs/manual/reference/command/rotateCertificates/#mongodb-dbcommand-dbcmd.rotateCertificates

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Send activity feed event by email similar to Alerts

    We need to be informed and or react on some activity feed events. So we want to either be able to configure alert on specific activity type and/or be able to push activity feeds somewhere similar to alerts. then we would be able to configure actions based on activity type.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. ops manager agent support for Rocky Linux

    Ops manager and Mongodb work on Rocky, but it seems there is no option for Rocky in the Ops Manager agent manifest, the current agent detects no Linux flavor for Rocky Linux. This already works on RHEL/CentOS and Rocky is supposed to be fully compatible with these OS's.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. The Ops Manager UI provide an option to trigger election (stepDown)

    Have the option to perform primary stepDown from Ops Manager UI to trigger election

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close