246 results found

1. Encryption at REST, KMIP alternative

   Hi,

   Currently, for a production Setup of MongoDB EA and Ops Manager, only option to enable Encryption at REST that would cover both the Replica Set and Backups in Ops Manager, is to use 3rd party application that has KMIP engine, which by itself usually is locked behind additional costs with enterprise licensing.

   I would like to suggest, that MongoDB could develop either an alternative feature for Encryption at REST which would enable anyone who has MongoDB Enterprise advanced license to have fully functional Encryption at REST for a production environment or A full KMS solution to leverage KMIP capabilities already present in Enterprise versions.

   P.S Ofcourse there is currently a local file encryption available, but that is only good for performance testing, and is not a valid option for a production environment, which needs both MongoDB data and backups encrypted at REST.

   Hi,

   Currently, for a production Setup of MongoDB EA and Ops Manager, only option to enable Encryption at REST that would cover both the Replica Set and Backups in Ops Manager, is to use 3rd party application that has KMIP engine, which by itself usually is locked behind additional costs with enterprise licensing.

   I would like to suggest, that MongoDB could develop either an alternative feature for Encryption at REST which would enable anyone who has MongoDB Enterprise advanced license to have fully functional Encryption at REST for a production environment or A full KMS solution to leverage KMIP capabilities… more

   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

   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

   Submit Rating

2. Prevent aggregation queries from appearing as poorly targeted queries

   When looking at query targeting aggregate group queries can show up incorrectly as poorly targeted. For example if I select all documents with a given client id and group them by null and sum a field (eg revenue) then if there are 1,000,000 documents that get summed up to return 1 agregate document then it considers the query targeting to be 1,000,000 because it scanned 1,000,000 documents and returned one. This is highly misleading however since the query used an index to find the exact 1,000,000 documents needed and then used every single one of those documents to generate the output.

   What I would like to see would be something more like Scanned documents/Used Documents.

   Or possibly for aggregate queries that involve a group stage (and maybe other things) rather than look at the final output document count it could instead look at how many documents were passed into the group stage (ie that were actually used).

   When looking at query targeting aggregate group queries can show up incorrectly as poorly targeted. For example if I select all documents with a given client id and group them by null and sum a field (eg revenue) then if there are 1,000,000 documents that get summed up to return 1 agregate document then it considers the query targeting to be 1,000,000 because it scanned 1,000,000 documents and returned one. This is highly misleading however since the query used an index to find the exact 1,000,000 documents needed and then used every single one of those documents to generate the… 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

   Submit Rating

3. Allow alerts based on CPU iowait in OPS manager

   Currently, there is no way to set alerts on CPU iowait in OPS Manager. When there's disk latency, cpu iowait usually shows an immediate and consistent spike. Alerting on cpu iowait can enable customers to promptly review and address disk latency.

   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

   Submit Rating

4. Add Ops Manager UI breadcrumbs to help with user navigation

   Breadcrumbs show the user where they are in the Ops Manager's (webpage) hierarchy.

   https://www.smashingmagazine.com/2009/03/breadcrumbs-in-web-design-examples-and-best-practices/

   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

   Submit Rating

5. Option to select the S3 Storage Class for snapshots and oplog slices

   Ops Manager currently uses S3 Standard storage for all snapshot storage and oplog storage and the storage class is not configurable.

   AWS has storage classes that are specifically designed for backups (lower storage costs, but higher retrieval costs) like GlacierInstantRetrieval.

   We could significantly reduce costs if we could select the Storage Class that Ops Manager would use when uploading data to S3.

   ---

   NOTES

   It is possible to create lifecycle rules in S3 to transition the objects from Standard Storage to another Storage Class, but this transition itself incurs a cost for the objects/bytes that are transitioned. This may reduce costs some, but not as much as if the objects used the desired Storage Class during creation.

   It is NOT possible to set a "default storage class" on an s3 bucket.

   Ops Manager currently uses S3 Standard storage for all snapshot storage and oplog storage and the storage class is not configurable.

   AWS has storage classes that are specifically designed for backups (lower storage costs, but higher retrieval costs) like GlacierInstantRetrieval.

   We could significantly reduce costs if we could select the Storage Class that Ops Manager would use when uploading data to S3.

   ---

   NOTES

   It is possible to create lifecycle rules in S3 to transition the objects from Standard Storage to another Storage Class, but this transition itself incurs a cost for the objects/bytes that are transitioned. This may reduce costs… more

   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

   Submit Rating

6. Surface Important Project Level Alerts Globally

   It is easy to miss global alerts if you are just using the Ops Manager UI and not seeing the emails, or if there is an email delivery issue. In fact, alerts like "Snapshots are behind", which may be days or weeks behind, are not surfaced anywhere in the UI unless you go and dig for them. I suggest adding a count in the top nav bar for critical alerts, or even all alerts.

   •  

   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

   Submit Rating

7. Allow SSL Cert Rotation Without Restarting The Agent

   It would be great if the agent could be sent a signal to pickup a new cert, or detect the cert changed via file watchers, instead of having to restart it.

   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

   Submit Rating

8. deployment metadata resync

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

   My reason for this suggestion:
   See Case: 01438273. One of my deployments had duplicate entries for all 3 nodes. We suspect that happened because we were initially using short name hostnames in the deployment's replica set definition and later changed that to FQDN hostnames. The original entries should have been removed from the AppDB collection, but instead they remained there indicating version 4.0.26, while new ones were created, which were then successively updated as the deployment got upgraded. When I tried to upgrade Ops Manager to v 8.0, it refused to restart because OM8 cannot handle MongoDB versions <4.4. The solution was to manually run a deleteMany operation in the AppDB which had to be provided by the development team.

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

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

   Submit Rating

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

   Submit Rating

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

    Submit Rating

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

    Submit Rating

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

    Submit Rating

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

    Submit Rating

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

    Submit Rating

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

    Submit Rating

16. The Backup Daemon auto downloads all old Mongodb versions

    If "Backup Versions Auto Download" is set to true on the Admin > General > Ops Manager Config > MISCELLANEOUS tab, then the backup daemon automatically downloads all older major versions of the software.
    In my opinion, it would be better if you could either select the version/s which you want or it only downloaded versions equal to or higher than your current version.
    All the old versions take up disk space and can only be deleted if the setting is changed to false.
    thanks

    1 vote

    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

    Submit Rating

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

    Submit Rating

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

    Submit Rating

19. Show better diff for changes to setParameter json blob

    The "review and deploy" step only shows that there IS a diff in the setParameter json, but it does not make it clear what is actually changing.

    It would be very helpful to show the diff between the two json payloads in an easy-to-read way.

    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

    Submit Rating

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

    7 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

    Submit Rating