441 results found

1. Lock enableLocalConfigurationServer setting on OPS Manager side

   To harden security for mongodb deployment managed by OPS Manager, we can use setting enableLocalConfigurationServer = true so automation-mongod.conf won't have any passwords for ssl certs and agent will retrieve them from OPS Manager.

   to disable this feature and to read all passwords for ssl certs (and hence get access to mongodb data) it's enough to comment out this parameter an restart automation service (or wait until host will be restarted).

   Linux root user can modify any file on mongodb host including this file and can restart any services, so it's impossible to protect getting all passwords and mongod.conf from root user only using Linux functionality.

   But it's possible to add feature in OPS Manager to "lock automation agent setting for enableLocalConfigurationServer" on OPS Manager side.

   Even if root comments out/disables this setting, automation agent will request full config file from OPS Manager and OPS Manager will check on its side if it's allowed to send full config back to agent.

   i.e. only MongoDB DBA who manages deployment from OPS Manager controls if full config with all password should be sent to host and Linux root user won't be able on their own retrieve passwords.

   To harden security for mongodb deployment managed by OPS Manager, we can use setting enableLocalConfigurationServer = true so automation-mongod.conf won't have any passwords for ssl certs and agent will retrieve them from OPS Manager.

   to disable this feature and to read all passwords for ssl certs (and hence get access to mongodb data) it's enough to comment out this parameter an restart automation service (or wait until host will be restarted).

   Linux root user can modify any file on mongodb host including this file and can restart any services, so it's impossible to protect getting all passwords and mongod.conf from… 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

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

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

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

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

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

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

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

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

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

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

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

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

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

16. Add milliseconds to Ops Manager access logs

    The current logback-access.xml file only logs with second grainularity, which isn't great when trying to correlate HTTP events with other log events.

    I propose changing this line:

    <pattern>%h %l %u [%t] "%X{requestUrl}" %s %b "%i{Referer}" "%i{User-Agent}"

    To this:

    <pattern>%h %l %u [%date{"dd/MMM/yyyy:HH:mm:ss.SSS Z"}] "%X{requestUrl}" %s %b "%i{Referer}" "%i{User-Agent}"

    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

17. Allow setting the backup PreferredMember via the API for sharded clusters

    It's currently only possible to set a backup PreferredMember via the API for a standalone replicaset, but it's not possible to set the PreferredMember for shards of a sharded cluster.

    You can do this via the Web UI, but that's incredibly tedious if you have many shards and it would also be valuable to be able to change the PreferredMember in automation scripts.

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

18. MONGOCLI add command to shutdown and startup the standalone instance

    in this moment there is no way to shutdown or startup a standalone instance because the mongocli works with cluster only

    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  ·  MongoDB CLI for Cloud Manager and 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

19. Examples for installing operator declaratively on argocd

    Hey there,

    Would it be possible to add some examples when it comes to deploying the community operator with argocd?

    Thanks

    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  ·  Other  ·  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. Support FlashBlade as the Storage API
    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