448 results found

1. Authentication support for OpenID connect (OIDC)

   I would like to connect to MongoDB as part of a Terraform IaC project from bitbucket pipelines. Currently this is possible only through API keys.

   It would be great if there was support for OIDC as it provides rotated keys and solid support of various pipelines (GitHub actions, Bitbucket pipelines, ...). Also with OIDC the client is not exposed to any credentials, so this would allow for a "zero-trust" approach when it comes to IaC (Infrastructure as Code).

   1 vote

   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  ·  Automation  ·  Edit…  ·  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

2. I found what I believe to be an error in the following document

   I found what I believe to be an error in the following document.
   https://www.mongodb.com/docs/ops-manager/current/tutorial/install-simple-test-deployment/

   In the section "5. Create the Ops Manager Application Database directory," it instructs to execute the following command
   sudo chown -R mongod:mongod /data

   In my environment, the mongod user does not exist and I get an error, but looking at the passwd file, the mongodb user and mongodb group seem to exist. The version is 11.7.

   I think the correct command is as follows
   sudo chown -R mongodb:mongodb /data

   1 vote

   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  ·  Edit…  ·  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. Operating System distribution and version of a host in OPS Manager API

   Hi,
   would be useful having the operating system distribution and version of a host for our automation scripts.
   This info is not available in any OPS Manager API request, as the case 01119828.
   My suggestion is add this info at "Get Host by ID" https://www.mongodb.com/docs/ops-manager/current/reference/api/hosts/get-one-host-by-id/
   Best regards,
   Danilo

   1 vote

   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  ·  Edit…  ·  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. Ability to mark a deployment as an INELIGIBLE restore target

   Restoring to a cluster is one of the few destructive actions that Ops Manager takes and it's terrifying to see our main production cluster listed as a possible restore target!

   I would love to be able to toggle a setting on this cluster to indicate that it is NOT available as a restore target.

   This could be similar to the AWS "DisableApiTermination" feature that prevents instance termination.
   https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/terminating-instances.html#Using_ChangingDisableAPITermination

   1 vote

   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  ·  Edit…  ·  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. Add flexibility to disable and enable specific fetures of managing mongodb instance in OPS Manager (like user Sync)

   Currently , Mongodb admin can not select to disable or enable feature after put mongodb manageed under OPS Manager. like security control .

   Normally , Security control is not mongodb or Ops manager admin's responsibility , which is managed by a enterprice access control team.

   1 , In opsmanager , there is not role for security control, like useradmin in mongodb.
   2 , When ACCESS control team create role in mongodb. Ops Manager sycn it back.
   3 , Opsmanager admin have to be engaged to work with ACCESS control team to complete the task.

   It is kind of not least previledge and seperation of duty.

   I would suggest to provide a feature to give Flexibility to disable and enable specific features of managing mongodb instance in OPS Manager (like user Sync), and other features, like configuration. Have parameter should be fine.

   Currently , Mongodb admin can not select to disable or enable feature after put mongodb manageed under OPS Manager. like security control .

   Normally , Security control is not mongodb or Ops manager admin's responsibility , which is managed by a enterprice access control team.

   1 , In opsmanager , there is not role for security control, like useradmin in mongodb.
   2 , When ACCESS control team create role in mongodb. Ops Manager sycn it back.
   3 , Opsmanager admin have to be engaged to work with ACCESS control team to complete the task.

   It is kind of not least… more

   1 vote

   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

6. There have been at least a few issues on Kubernetes Community Operator related to PVC expansion, yet this is not documented anywhere.

   There have been at least a few issues on Kubernetes Community Operator related to PVC expansion, yet this is not documented anywhere.

   Looking at closed issues, one may get an idea that this operation is impossible, but with the latest CSI it should be - it requires some handcrafting. On the other side Enterprise operator has this covered here - https://www.mongodb.com/docs/kubernetes-operator/stable/tutorial/resize-pv-storage/. I suggest writing similar how-to for the Community operator.
   My currently tested workflow for volume expansion is similar to this explained on the page above, but as for my knowledge Community operator doesn't allow this operation - as it will recreate StatefulSet when you delete, and there's no way for pause reconciliation of MongoDBCommunity. So it requires you to scale down operator deployment for the time of expansion.

   So it looks like this:
   1. Scale down mongodb-kubernetes-operator to 0
   2. Dump current mongodb StatefulSet specs to file
   3. Delete StatefulSet leaving pods (--cascade=orphan)
   4. Modify saved StatefulSet specs in the file and update volumeClaimTemplates to match your new size requirements

   And here it splits, as I'm using Longhorn, and it needs some time to detach and resize the volume. Because of that, using rollout - as described on the Enterprise operator hasn't worked. So for possibly any other CSI plugin, you should continue as described on the page:

   1. Patch PVCs with the new size
   2. Re-create StatefulSet with new specs for volumeClaimTemplates
   3. Rollout restart StatefulSet

   But in my case, it was like this:

   1. Delete one pod (secondary RS members first, primary last - as usual)
   2. Wait for PV to be in a detached state
   3. Patch PVC
   4. Wait for PV to resize
   5. Re-create StatefulSet with new specs for volumeClaimTemplates
   6. Wait for it to reconcile
   7. Delete StatefulSet, leaving pods again
   8. Repeat the above steps for any other pods in your StatefulSet

   And finally, make changes to MongoDBCommunity specs to match those in the manually created StatefulSet and scale-up operator.

   There have been at least a few issues on Kubernetes Community Operator related to PVC expansion, yet this is not documented anywhere.

   Looking at closed issues, one may get an idea that this operation is impossible, but with the latest CSI it should be - it requires some handcrafting. On the other side Enterprise operator has this covered here - https://www.mongodb.com/docs/kubernetes-operator/stable/tutorial/resize-pv-storage/. I suggest writing similar how-to for the Community operator.
   My currently tested workflow for volume expansion is similar to this explained on the page above, but as for my knowledge Community operator doesn't allow this operation - as… more

   1 vote

   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  ·  Enterprise Kubernetes Operator  ·  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
   planned  ·  AdminDan (Admin, MongoDB) responded

   Planned - no fixed date but likely complete within Q2.

7. Build Ops Manager packages for ARM architecture

   The new Graviton instance types in AWS seem very promising from a cost/peformance perspective. We would love to be able to run our Ops Manager cluster on these new instance types, but there currently aren't any packages available for ARM architectures!

   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

8. Ability to start the bi connector using a .drdl file in Ops Manager

   Ability to start the bi connector using a .drdl file in Ops Manager. Currently only possible with en premise bi connector deployment(mongosqld).

   1 vote

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

10. Add possibility to configure the process hostnames for the automation config map

    In order to use external certificates could it be possible to configure the process hostnames in automation config map

    1 vote

    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  ·  Edit…  ·  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. TLS secret key config

    Add option to configure the secret keys for the server and CA certificate and replace the default ones tls.crt, tls.key and ca.crt

    1 vote

    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  ·  Edit…  ·  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. Send Alerts When Network Access is Updated

    Create an alert when IP Addresses are added or removed from a cluster network access whitelist.

    1 vote

    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  ·  Monitoring / Alerts  ·  Edit…  ·  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. Add "Cluster Tier" and Provisioned "IOPS" as options in MongoDB Metrics Charts in Atlas

    If these charts were available, it would enable to the user to visualize the Tier and IOPS of the cluster during specific time ranges, and compare to other metrics such as CPU, iowait, etc.

    In my team's experience, we use Atlas auto-scaling to allow a cluster to scale up/down based on load, but when looking at Metrics it is not clear which Tier the cluster was in (e.g. "M30") when evaluating other metrics like CPU utilization. We are able to manually track Cluster Tier by viewing the Project Activity Feed, but if this data was integrated into Metrics it would be great for comparison.

    If these charts were available, it would enable to the user to visualize the Tier and IOPS of the cluster during specific time ranges, and compare to other metrics such as CPU, iowait, etc.

    In my team's experience, we use Atlas auto-scaling to allow a cluster to scale up/down based on load, but when looking at Metrics it is not clear which Tier the cluster was in (e.g. "M30") when evaluating other metrics like CPU utilization. We are able to manually track Cluster Tier by viewing the Project Activity Feed, but if this data was integrated into Metrics it would… more

    1 vote

    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  ·  Monitoring / Alerts  ·  Edit…  ·  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. Add Ops Manager alert on tlsX509ExpirationWarningThresholdDays client

    Ops Manager alert, for messages posted through 'tlsX509ExpirationWarningThresholdDays' parameter to warn for client certs expiry

    1 vote

    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  ·  Edit…  ·  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. Ops Manager Load Balancer

    In the same way we can connect to a replica set via a connection string containing the 3 hostnames of the members (in a 3 member replica set) which indicates some load balancing built in, it would be good to allow automation agent's mmsBaseUrl parameter to accept 3 Ops Manager web app hostnames if Ops Manager was running in 3 nodes on top of a 3 member replica set OM Application DB. With this, if one of the 3 Ops Manager web apps fails, the agent's connection to OM will be uninterrupted. Currently we will have to configure our own load balancer, or manually update the agent's mmsBaseUrl if the current OM fails both of which are tedious setups.

    In the same way we can connect to a replica set via a connection string containing the 3 hostnames of the members (in a 3 member replica set) which indicates some load balancing built in, it would be good to allow automation agent's mmsBaseUrl parameter to accept 3 Ops Manager web app hostnames if Ops Manager was running in 3 nodes on top of a 3 member replica set OM Application DB. With this, if one of the 3 Ops Manager web apps fails, the agent's connection to OM will be uninterrupted. Currently we will have to configure our own… more

    2 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. Allow Enterprise Kubernetes Operator to downgrade FCV
    2 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  ·  Enterprise Kubernetes Operator  ·  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. Ops Manager API should be authenticated via Certificate

    Ops Manager API uses HTTP Digest Authentication, this method requires a username and a password which are hashed and provided in the form of registered Ops Manager account, and the password which is a Public API Key associated with that account.

    But as part of security feature we should be allowed to use Authentication based on SSL certificates as we are using for Client connection, This will help to secure the self automation process if we are developing any internally.

    3 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. Add recommended ulimit settings to the systemctl service definition

    The Ops Manager documentation recommends higher than default ulimit settings, so why not include these in the systemctl service definition?

    https://www.mongodb.com/docs/ops-manager/current/core/requirements/index.html#ulimits-requirements-for-application

    2 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

19. Disk metric - log drive

    The ops manager is not capturing the log drive disk related metrics when the log path is different from data path. This is an important metric to monitor for anyone to consider OM as the monitoring tool.

    1 vote

    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  ·  Edit…  ·  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. add logical name to disk in metrics

    when we look at hardware metric in replicaset, OPS Manager displays and groups disk stats based on internal disk name on each node. if for some reason we have disks discovered in different order on OS level, disk names will be different and it's become very messy and difficult to compare disk stats between different nodes.

    Suggestion is to add ability to give disk logical name so OPS Manager will display disks for data and disks for logs in a nice way. if new disk is replaced or added - default name can be displayed so administrator will be able to assign or re-assign logical name to disk.

    for example, instead of
    Disk IOPS - nvme2n1
    it will display
    Disk IOPS - data

    when we look at hardware metric in replicaset, OPS Manager displays and groups disk stats based on internal disk name on each node. if for some reason we have disks discovered in different order on OS level, disk names will be different and it's become very messy and difficult to compare disk stats between different nodes.

    Suggestion is to add ability to give disk logical name so OPS Manager will display disks for data and disks for logs in a nice way. if new disk is replaced or added - default name can be displayed so administrator will be able… more

    1 vote

    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  ·  Edit…  ·  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