469 results found

1. Authentication mode MONGODB-OIDC

   Support for authentication: MONGODB-OIDC

   security:
   authentication:
   enabled: true
   modes:
   - "MONGODB-OIDC"

   currently we get the following error wir kuberntes operator 1.26.0, OpsManager 7.0.7 and RS 7.0.11:
   Unsupported value: "MONGODB-OIDC"

   9 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

   3 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
   under review  ·  AdminDan (Admin, MongoDB) responded

   We're considering this for inclusion into Q4 (by end of January) - but we're currently reviewing priorities for a number of projects competing for attention.

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

3. Alert for even number of voting members of a Replica Set

   Alert for even number of voting members of a Replica Set

   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

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

   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

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

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

   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

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

   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

8. Add a possibility to download all snapshots for deployment/project/organisation

   Currently, it is not possible to move between S3 buckets without to terminate the job. It would be great to have possibility to download all the snapshots before to delete backup job.

   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  ·  Backup  ·  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. Currently the OM App server has the secrets to connect to S3. This is a security issue for many organizations.Can a secure vault be used t

   Currently the OM App server has the secrets to connect to S3. This is a security issue for many organizations.Can a secure vault be used to store the secret?

   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

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

    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

11. Allow to select columns visible on OPS Manager All projects page

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

    We need ability to select only few columns visible on this page.
    Example:
    cluster name, data size

    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

12. All projects page in MongoOPS should show if encryption at rest is enabled

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

    We need to see if encryption-at-rest is enabled.

    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

13. 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 you get when you run "hostname -f" ("Seed node - hostname:port =>Use fully qualified domain name (value returned from hostname -f). Must be unique and resolvable from any server within your deployment that is running a MongoDB Agent."), but when you do it that way, as Ops Manager uses the "hello" command to discover the nodes, what you get are the servers with the service network domain, which cannot be connected to for security reasons in your organization.

    We need, when adding an existing deployment, to connect to the rest of the nodes using the operation network instead of the service network. We cannot assign the domain to the hostname or register the replica set nodes in MongoDB with the operation domain due to internal security reasons, as mentioned above. We cannot modify the hostname domain either due to automatization reasons and backbone tasks of our organization.

    You have more details about this in your internal case https://hub.corp.mongodb.com/case/01288897 and in our case https://support.mongodb.com/case/01288897 (please, see comments too).

    Thanks and best regards.

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

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

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

    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

16. Create an option to turn ON/OFF daily snapshots schedule from "Ops Manager- Continuous Backup - Edit snapshot schedule"

    Currently, we have the option to take daily snapshots at different intervals (6 hrs, 8 hrs, 12, hrs, 24 hrs) but we do not have an option to not configure daily snapshots. While daily snapshots are considered essential, we have almost 200 replica sets of different DB sizes and the daily snapshots, tend interfere with itself due to large DB size and not completing itself in good time for the next day's daily snapshot to run. So if we turn off the daily snapshot or tune the frequency of the daily snapshots on select large replica sets, we will avoid the backup from failing and we can at least ensure the weekly full backup is successful on these very large DBs.

    Currently, we have the option to take daily snapshots at different intervals (6 hrs, 8 hrs, 12, hrs, 24 hrs) but we do not have an option to not configure daily snapshots. While daily snapshots are considered essential, we have almost 200 replica sets of different DB sizes and the daily snapshots, tend interfere with itself due to large DB size and not completing itself in good time for the next day's daily snapshot to run. So if we turn off the daily snapshot or tune the frequency of the daily snapshots on select large replica sets, we will avoid… more

    10 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  ·  Backup  ·  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. Add specific label to Arbiter deployment to distinguish it label-wise

    As per https://github.com/mongodb/mongodb-kubernetes-operator/issues/1442 we would like to request to either and/or:

    a) have the operator add a new label to replica and arbiter statefulset deployments to distinguish them from each other
    b) have the ability to add your own labels to specifically the replica OR the arbiter statefulset deployments

    Having the ability to easily filter arbiter statefulsets from non-arbiter statefulsets would be great. This is useful for example for backup tools that run commands on pods based on a combination of labels, to exclude any arbiters from backup.

    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

    1 comment  ·  Community 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

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

    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

19. Publish Ops Manager deployments to Slack

    It would be nice if the Slack integration could be used to post deployment notices to a Slack channel.

    We have a channel where our other tooling posts about changes that have been made, and there isn't an easy way to have Ops Manager do the same.

    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

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

    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